> > > > One could write the mode into some sort of NVRAM on the board, but if > > > > this is the system console, you have a catch-22. You need a display to > > > > show you what you are about to write to the board that controls the > > > > display. > > > > > > You can always put the card into a PC in which it won't be the primary > > > display and you can use the NVRAM or flash it with videobios or fpga > > > binary which will implement your specific monitor timing right after boot. > > > > That is probably acceptable for most users of the OGD board. > > It will not be acceptable for OGC users. > > Well, there is the risk of hosing your BIOS, but the same tool that > you would use to program the custom video modes would also be able to > restore the whole BIOS to the latest revision. Why is that a problem > for OGC? Or is it not a technical problem...?
I'm thinking that users of OGD are likely to have extra hardware lying around that could be used to do the initial programming of the OGD. I'm thinking that users of OGC are less likely to have extra hardware lying around. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
