Many DSTDs use the _OSI and \_OS_ methods to check for a certain
OS-Type. I have never seen them check for anything else than Windows.
How does the Linux ACPI driver handle this? Is it necessary to patch a
DSTD to make some features available to Linux?
Okay, I just included some Debug statement into my DSDT.
_OSI is not supported.
\_OS_ equals "Linux"
Some sections in my DSDT (see attachment) are not executed on Linux.
This is the (decompiled and fixed) DSDT of an Acer TM630.
Isn't it a strange world where the BIOS is specific to an OS? And I
thought the OS should adapt to the hardware and not vice versa...
From: Ducrot Bruno <ducrot@po...> - 2003-05-30 08:34:25
On Fri, May 30, 2003 at 01:42:47AM +0200, Ortwin Glück wrote:
> Okay, I just included some Debug statement into my DSDT.
> _OSI is not supported.
> \_OS_ equals "Linux"
> Some sections in my DSDT (see attachment) are not executed on Linux.
> This is the (decompiled and fixed) DSDT of an Acer TM630.
> Isn't it a strange world where the BIOS is specific to an OS? And I
> thought the OS should adapt to the hardware and not vice versa...
This _OS stuff is pure crasp IMHO. The _OSI method is a Microsoft
extension, and is documented somewhere in their site. As for
_OS, that is only crasp.
Note that you can pass the acpi_os_name='' if you want
to change _OS so that some method may work 'better' for you.
Sometimes, it may help to try others values, but YMMV.
Note also that only some thinkpads have _OS == 'Linux' related
stuff implemented in their DSDT, but it seems that it is not
well used though (at least, IBM do care of that, even
if it is not perfect).
I don't find that others vendors do care of others OS other
than redmond' one. But it is for laptops/desktop word.
To be fair, _OS seems not to be used in servers.
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.