Pavel Machek [off-list ref] wrote:
quoted
Open Firmware may be a 'nicer' solution, but I guarantee that if the
vendors started supporting that it would be just a bug ridden as any 16-
bit real mode BIOS code. For the Video BIOS the code always works for
what it is tested for. Some vendors spend more time testing the VBE BIOS
side of things fully (if they are smart they have licensed our VBETest
tools for this purpose). Unfortunatley some vendors do not test this
stuff thoroughly and it has problems. But the same testing issues would
exist whether the firmware was written as a 16-bit x86 blob or as an Open
Firmware blob.
Actually that 16-bit x86 blob can access any PC hardware, and that's
where the stuff gets hard.
Yes, but there is only a very small set of PC hardware features you need
to implement, and most BIOS'es only look at those things for timing
purposes. Unfortunately there is no standard for how BIOS'es do internal
timing and delay loops, so we emulate them all (8253 timers, speaker
ports and CMOS time/date support ;-).
When we come across a new card that doesn't work we figure out why and
make new additions to the video boot code. However at this point we think
we have covered just about every card out there, as I don't think there
are any cards in our labs that don't work at present. If there are,
fixing them is just a matter of spending the time to debug it.
Regards,
---
Kendall Bennett
Chief Executive Officer
SciTech Software, Inc.
Phone: (530) 894 8400
http://www.scitechsoft.com
~ SciTech SNAP - The future of device driver technology! ~
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl