yeah, right... then you need an XML parser in the driver... somehow I
don't think the kernel people will think it's a good idea...
I am in no way shape or form arguing for XML, but:
Would not the part that sits in the kernel ideally only need to know how
to manage transfers from user space to kernel space and handle errors
gracefully? If an invalid command for a non-existent functional unit is
invoked by a series of uploaded commands a standard error could be
thrown by the hardware and handled by the kernel. X could be entrusted
to parse a hardware description and figure out how to best utilize the
hardware available.
The only bits that would have to be standardized between compatible
variants would be the hardware that provides a dumb framebuffer for the
kernel managed console, the command/data upload/download hardware, the
error handling protocol/mechanism, and perhaps the mechanism for
changing video modes. Compared to the total hardware that can exist on
the card, this is pretty minimal.
-John
--
John R. Culp
[EMAIL PROTECTED]
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)