From: Theodore Tso <tytso@MIT.EDU>
To: Len Brown <lenb@kernel.org>
Cc: "Dmitry A. Marin" <corvax@corvax.ru>, linux-acpi@vger.kernel.org
Subject: Re: dmidecode output from Benq notebook
Date: Mon, 21 Jan 2008 02:51:34 -0500 [thread overview]
Message-ID: <20080121075134.GC8105@mit.edu> (raw)
In-Reply-To: <200801201408.40945.lenb@kernel.org>
On Sun, Jan 20, 2008 at 02:08:40PM -0500, Len Brown wrote:
>
> OSI(Linux) has no effect on the AML of this machine,
> as OSYS is over-written. So I'll just kill the warning
> on this box by adding it to the NOP DMI list.
The one thing I worry about is if you aren't including the BIOS
version in the DMI list, you could end up in a situation where one
version of the BIOS treats OSI(Linux) as a no-op, but a newer or an
older version of the BIOS actually does something with it....
BIOS writers can be sneaky that way. :-)
- Ted
next prev parent reply other threads:[~2008-01-21 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 10:40 dmidecode output from Benq notebook Dmitry A. Marin
2008-01-18 23:56 ` Len Brown
[not found] ` <web-56975710@backend13.aha.ru>
2008-01-20 19:08 ` Len Brown
2008-01-21 7:51 ` Theodore Tso [this message]
2008-01-21 23:22 ` Len Brown
2008-01-22 15:29 ` Theodore Tso
2008-01-23 5:39 ` Len Brown
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=20080121075134.GC8105@mit.edu \
--to=tytso@mit.edu \
--cc=corvax@corvax.ru \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.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