On Dec 9, 2007 7:14 PM, <[EMAIL PROTECTED]> wrote: > This does not seem to be a terribly efficient method for memory control, > unless I'm missing something.
What is inefficient about it? The memories have to be controlled in a certain way, and to keep clock rates up, things have to be deeply pipelined. The memories are a single resource that must be accessed efficiently by multiple agents, hence the arbiter. What specifically are you objecting to? > Is there a blitter for handling the memory needs? Is it FIFO, SIMD or Vector > based? There is no blitter YET. But there will be. We're not quite there yet. Actually, it'll be more than a blitter. -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
