public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Alex Williamson <alex.williamson-VXdhtT5mjnY@public.gmane.org>
Cc: linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] restore _OS object to "Linux" for ia64
Date: 13 Sep 2004 15:22:30 -0400	[thread overview]
Message-ID: <1095103349.2512.16.camel@d845pe> (raw)
In-Reply-To: <1095100068.20631.30.camel@tdi>

On Mon, 2004-09-13 at 14:27, Alex Williamson wrote:
>    A recent change to ACPI made the _OS object falsely report the OS as
> "Microsoft Windows NT".  This seems like a slippery slope, and I'd
> rather not go down it for ia64.  I think all of the ia64 OEMs are
> involved enough with Linux that this isn't necessary and the change
> limits the options should ACPI firmware need to make an OS specific work
> around.  The patch below will make all ia64 boxes report a default _OS
> of "Linux".

While I share your pride in Linux, there are a couple of reasons
why we do not make _OS return "Linux".

_OS is a deprecated interface -- it has been replaced
by the more flexible _OSI.  So with _OS we're talking
about past, not future systems.  And there is a total
population of 0 systems in the installed base that check
for _OS ="Linux" in their firmware.  On the other hand, there
are zillions of systems that check for Windows with _OS,
and the !Windows path through the firmware is effectivly
unvalidated.

While this is really important on i386, it may not be
important for ia64.  However, unless you can show
me an existing system that checks for _OS=Linux, then
it only adds risk w/o reward to make this change, even
if just on ia64.  New systems should be using _OSI.

thanks,
-Len




-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php

  reply	other threads:[~2004-09-13 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13 18:27 [PATCH] restore _OS object to "Linux" for ia64 Alex Williamson
2004-09-13 19:22 ` Len Brown [this message]
2004-09-13 19:42   ` [ACPI] " Alex Williamson
  -- strict thread matches above, loose matches on Subject: below --
2004-09-13 22:11 Moore, Robert
2004-09-13 22:59 Moore, Robert

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=1095103349.2512.16.camel@d845pe \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=alex.williamson-VXdhtT5mjnY@public.gmane.org \
    --cc=linux-ia64-u79uwXL29TY76Z2rM5mHXA@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