From: Huw Rogers <count0-tC47gz4GrgtWk0Htik3J/w@public.gmane.org>
To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: _OSI and _OS DSDT methods
Date: Sat, 07 Feb 2004 16:04:26 -0500 [thread overview]
Message-ID: <20040207155315.5250.COUNT0@localnet.com> (raw)
In-Reply-To: <00d101c3ed98$3a226390$21b35452-0YB+lduMvyg@public.gmane.org>
The _OSI method is used in my DSDT in addition to the OS name returned
by the _OS method (http://www.microsoft.com/whdc/hwdev/tech/onnow/_OSI-method.mspx).
The results influence the behaviour of many other methods in the DSDT,
including sleep/wake methods. This OSFL() method is called and if/else
blocks depend on the return value:
Name (OSVR, Ones)
Method (OSFL, 0, NotSerialized) {
If (LNot (LEqual (OSVR, Ones))) {
Return (OSVR)
}
Store (0x01, OSVR)
If (MCTH (\_OS, "Microsoft Windows NT")) {
If (LEqual (OSVR, 0x01)) {
If (CondRefOf (_OSI, Local0)) {
If (\_OSI ("Windows 2001")) {
Store (0x04, OSVR)
}
} Else {
Store (0x00, OSVR)
}
}
} Else {
If (MCTH (\_OS, "Microsoft WindowsME: Millennium Edition")) {
Store (0x02, OSVR)
}
}
Return (OSVR)
}
What should Linux return for _OS and _OSI? Should 2.6 mimic Windows XP?
Does it?
-Huw
--
Huw Rogers <count0-tC47gz4GrgtWk0Htik3J/w@public.gmane.org>
-------------------------------------------------------
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
prev parent reply other threads:[~2004-02-07 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 22:35 ACPI, Acer Aspire 1700 series and Kernel 2.6 Henny Wilbrink
2004-02-07 16:33 ` gava-7azNGskkaze/k5lE4H/icg
[not found] ` <00d101c3ed98$3a226390$21b35452-0YB+lduMvyg@public.gmane.org>
2004-02-07 21:04 ` Huw Rogers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040207155315.5250.COUNT0@localnet.com \
--to=count0-tc47gz4grgtwk0htik3j/w@public.gmane.org \
--cc=acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox