Eric W. Biederman wrote:
the idea we toyed with was a generic callback which would enable this specific feature... still it was somewhat tricky given that ADLO sometimes loads itself over the LinuxBIOS
For V2 every port I have done has simply left those areas enabled as RAM, which obviates the need for any call backs.
I don't think thats enough. You have to route reads to the bios area and writes to RAM and then when its done route reads back to RAM so ADLO has to mess with some registers.
That code is not motherboard specific it is cpu/chipset specific, which is something else entirely.
Yeah. motherboard was the wrong term. You used it first though. *grin*
Any significant changes like always leaving the shadow areas enabled, we can easily implement in both v1 and v2. And things like pirq tables can be copied from wherever LinuxBIOS puts them. If it would help we can place pointers to the information in the LinuxBIOS table to make things easier to deal with.
pointers to code that would enable/disable the various functions? or pointers to some data struct that would instruct the code how to do then enable/disable?
They can be pretty different. On the matsonic 7308e motherboard this was a simple out() to a location. With the 440bx chipset this is a config space write.
_______________________________________________ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
