Len Brown wrote:
Thomas,
re: OSI(Windows...)
Thomas,
I discussed this with Len here in Ottawa. First I fully agree with his
reasoning for the current behaviour.
The main problem with OSI(Linux) is that it would be a quickly moving
target so checking for it wouldn't really help the BIOSes.
Still there might be special cases where BIOSes will still check (e.g.
if they intend to work with specific distribution releases which might
have specific bugs). Or to check for specific Linux features.
One way to do the later would be to define new OSI flags for specific
features. Haven't got a good proposal for that currently, but it's a
possibility.
The other thing that could be done is to define OSI flags specific for
special distribution releases so BIOSes could potentially check for bugs
in SLED10 or RHWS5 or something like this, which are hopefully stable
in that behaviour doesn't move as quickly. The way to do that wouldn't
be to change the kernel though, but just specify them on the command
line using acpi_osi=...
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
