On Wednesday 26 July 2006 09:41, Daniel Rozsnyó wrote: > Attila Kinali wrote: > > Now, i had an idea on how this issue could be solved. > > My idea is to have three registers with flags, telling which > > functionality is available and which is not. First register is > > for mandatory functionality that the driver has to support. If > > there is one function it does not know about, it should reject > > the device. The second register is for functionalities that are > > optional. Not being able to support one of these does not matter > > for the the correct functioning of the rest of the card. > > The third register is development space for those who are working > > on the code and add additional functionality. So they can test > > their subsystem until they are assigned an official bit in one > > of the two other registers. > > Maybe it would be better to store a hardware description in form of > XML into the flash, which could be downloaded by the driver. This > "document" will contain something like `lspci` - but inside the > openhardware board. I prefer to use of XML, because it can store easily
Hmm... XML is better suited for transmitting data between dis-similiar applications. IMO using it in an embedded way, local DB, configuration file ets is wasteful and un-necessary. Sorry... Just My Opinion... Heirachy can be encoded in a binary structure fine. Look at SNMP... Hamish.
pgpyknnnAM1G5.pgp
Description: PGP signature
_______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
