On Thursday 17 January 2008 07:28, Matthew Garrett wrote:
> On Thu, Jan 17, 2008 at 05:24:50AM -0500, Len Brown wrote:
>
> > + {
> > + .callback = dmi_enable_osi_linux,
> > + .ident = "Lenovo ThinkPad T61",
> > + .matches = {
> > + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> > + DMI_MATCH(DMI_PRODUCT_VERSION, "ThinkPad T61"),
> > + },
> > + },
> > +
>
> If we add it for specific devices, aren't vendors going to assume that
> future versions of that device will also be able to rely on this
> behaviour?
When the new product comes out and they
try Linux on it, OSI(Linux) will return FALSE unless
somebody (later) adds the new product to the white-list.
So if a vendor really cares about Linux, they'll know
during development that they can't count on OSI(Linux) returning TRUE.
> I'm very reluctant to add whitelisting - I suspect it makes
> more sense for us to just be compatible with Windows. My experiments
> with the T61 suggested that it was possible to get everything working
> without this, but I'll need to go back and check what the behaviour
> actually was to be sure.
I agree that white-lists are horrible.
And I blame myself for not deleting OSI(Linux) before 2.6.23.
For pandora's box has been opened and when OSI(Linux)
went into a reference BIOS, and it will be difficult to close
it to get back on the "Windows compatible" track
that makes the most sense for Linux.
Happily, most of the cases I've seen are simply NOP code inherited
from a reference BIOS, but in some cases the OEM really
did test with (some version of) Linux and made firmware
changes to make their product function properly.
I think there are just a few of these cases, and
I think it is actually more common to see systems
where OSI(Linux) causes random BIOS behaviour.
The later case is the one we need to fear, and
why we need to be dilligent about stamping out OSI(Linux)=TRUE.
But at the same time, I think we really need a whilte-list
to make some products ship. I believe that we'll
see an example from Dell shortly on S3 video restore.
I may not have been noticed yet b/c they're running pre-2.6.23.
I expect most of the "white-list" entries will actually just
document the casese where OSI(Linux) is presnet, but has no effect.
The white-list action in that case is simply to disable the warnings
and request for testing.
-Len
-
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
