On Dec 9, 2007 9:47 PM, <[EMAIL PROTECTED]> wrote: > > 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? > > Not obbjecting, just not seeing any control bits, but then again, I haven't > studied the design enough.
It has the control bits it needs. > Would you like a blitter design I've been working on? It's vector-based > (derived from the old Amiga blitter) and should be pretty quick. Well, I have something in mind that works with our architecture, but describe for us how yours works and maybe we can at least get some good ideas from it. Thank you for the offer! -- 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)
