Does Linux make use of the S3D methods?

[John Knottenbelt <jak97-CezfXpuMXD6Fxr2TtlUqVg@public.gmane.org>]

Hi

I have been inspecting my DSDT and I noticed this:

Scope(\_SB_) {
    Device(PWRB) {
        Name(_HID, 0x0c0cd041)
        Method(_STA) {
            Return(0xb)
        }
    }
    Device(PCI0) {
        Name(_HID, 0x030ad041)
        Name(_ADR, 0x0)
        Name(_BBN, 0x0)
        Method(_S3D) {
            If(OSFL) {
                Return(0x2)
            }
            Else {
                Return(0x3)
            }
        }

The ACPI spec says that the _S3D method returns the highest power saving level 
that the device can be put into. As you can see from the above (and other 
similar S3D methods) the result depends on the OSFL variable, which is 
defined with:

         Method(_INI) {
            \_SB_.PCI0.SBRG.IODT()
            If(MCTH(\_OS_, "Microsoft Windows NT")) {
                Store(0x0, OSFL)
            }
            Else {
                If(MCTH(\_OS_, "Microsoft Windows")) {
                    Store(0x1, OSFL)
                }
                Else {
                    If(MCTH(\_OS_, "Microsoft WindowsME: Millennium Edition"))
                   {
                        Store(0x2, OSFL)
                    }
                    Else {
                        Store(0x3, OSFL)
                    }
                }
            }
        }

So for under Linux, the OSFL will be 3, and _S3D methods will return 2. My 
question is, does the kernel make use of this information at all? Is it worth 
editing the DSDT so that OSFL=0 (i.e. Windows NT) ?

Thanks

John



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn