On 7/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Since the Tool under this scenario is a stand-alone product, and not part of any OGD or OGC board, it could be sold under its own part number, and be permanently installed in any system that requires it. Maximum flexibility for the end user. It wouldn't even be tied to PCI graphics boards; it could be compatible with any graphics board that uses a TRV10 or an FPGA emulation of it. In fact, the Tool board would be so generic, it could be used to configure products that have nothing to do with graphics. Should we start talking about an "OGT1"? Should there be a little header on OGD1 to permit plugging extra devices onto the end of the SPI chain? (I really hesitate to think about any changes to OGD1 now, but an SPI header might be put on the features list for a possible OGD2.)
I think you're making this MUCH more complicated than it needs to be. We have a programmable video controller and a programmable flash. Let's just use them what they're designed for, which is to be programmable. If they're booting in a BIOS-supported platform (like x86), we or they can use a tool to mod the firmware to insert a custom video mode. If they're booting in something else, the card won't be programmed until the kernel driver hits it anyway. In that case, they can just have the software configured correctly. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
