From: Nate Lawson <nate@root.org>
To: Gerald Pfeifer <gp@suse.de>
Cc: "Moore, Robert" <robert.moore@intel.com>,
"Brown, Len" <len.brown@intel.com>,
Alex Williamson <alex.williamson@hp.com>,
linux-ia64@vger.kernel.org,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: [ACPI] [PATCH] restore _OS object to "Linux" for ia64
Date: Mon, 13 Sep 2004 15:19:29 -0700 [thread overview]
Message-ID: <41461CF1.1000104@root.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0409132325261.11103@lifschitz.suse.de>
Gerald Pfeifer wrote:
> On Mon, 13 Sep 2004, Moore, Robert wrote:
>
>>Not only is the !Windows code path apparently untested for the most
>>part, we have discovered many machines that simply do not work properly
>>unless we report "Microsoft Windows NT" for the _OS string.
>
> Can you name some of these (broken) systems?
>
> Given that we apparently did not encounter this with our 2.6.5-based SLES9
> kernel so far, I'm a bit sceptical that many (if any) ia64 machines are
> affected.
The only ones I've seen have been i386. One was a broken irq routing
mechanism in the !windows case. It's likely the case that there are no
broken ia64 machines. But it's also likely that no ia64 systems read
\_OS so why should it matter what we put there? I agree with Len, if
you need to key off something OS-specific for Linux, use \_OSI.
--
Nate
next prev parent reply other threads:[~2004-09-13 22:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 19:37 [ACPI] [PATCH] restore _OS object to "Linux" for ia64 Moore, Robert
2004-09-13 21:30 ` Gerald Pfeifer
2004-09-13 22:19 ` Nate Lawson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-17 17:18 Moore, Robert
2004-09-14 15:00 Moore, Robert
2004-09-13 22:59 Moore, Robert
2004-09-14 4:27 ` [ACPI] " Alex Williamson
2004-09-13 18:27 Alex Williamson
2004-09-13 19:22 ` Len Brown
2004-09-13 19:42 ` [ACPI] " Alex Williamson
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=41461CF1.1000104@root.org \
--to=nate@root.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=alex.williamson@hp.com \
--cc=gp@suse.de \
--cc=len.brown@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=robert.moore@intel.com \
/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