Timothy Miller wrote: >> Here is another though. Rather than include immediate values in the >> opcodes, use a register bank. Something like this: > > Oh, interesting. I hadn't thought of that. The only reaction I have > right off is that it might not be possible due to the fact that we're > talking about the critical path in the controller. That is, we could > jam it in there, but the extra levels of logic would make the max > clock rate too slow. Still, it's an elegant idea.
This is not needed to be in HW, because each register value is already in video controller's program memory, so the application only needs to modify those bits. The whole thing could be solved with maintaining a table of offsets for the "registers" inside the program. (it might depend on whenever the program memory can be modified per instruction or only as a whole block - at least, the second allows us to change more "registers" atomically;) Daniel _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
