From: Derek Broughton <dbroughton-F3m4/jXepmf3fQ9qLvQP4Q@public.gmane.org>
To: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: Re: RE: [PATCH] [2/2] Allow override acpi_gbl_pre_defined_names (aka change that _OS).
Date: Wed, 05 Feb 2003 16:40:30 -0400 [thread overview]
Message-ID: <016901c2cd56$d2ee4f70$3746028e@bio.dfo.ca> (raw)
In-Reply-To: F760B14C9561B941B89469F59BA3A84725A15A@orsmsx401.jf.intel.com
From: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > From: Ducrot Bruno [mailto:ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org]
> > This is the linux part. It permit to pass a apci_os_name= boot args
> > in order to override the \_OS.
>
> I'm still not clear on why this needs to be changeable at runtime. If we do
> decide that the BIOS writers are so Windows-centric that we need to
> masquerade as one, why wouldn't we just change the #define and recompile?
Because many of us have Windows-only BIOSes, and really prefer NOT to recompile.
If not for ACPI, I would be using pre-packaged kernels.
I like Ducrot's idea :-)
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-02-05 20:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 18:55 [PATCH] [2/2] Allow override acpi_gbl_pre_defined_names (aka change that _OS) Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84725A15A-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-02-05 19:27 ` Ducrot Bruno
2003-02-05 19:50 ` Matthew Wilcox
2003-02-05 19:50 ` Dave Jones
2003-02-07 17:53 ` Pavel Machek
2003-02-05 20:40 ` Derek Broughton [this message]
[not found] ` <016901c2cd56$d2ee4f70$3746028e-dP0OE4Ef7fWw5LPnMra/2Q@public.gmane.org>
2003-02-05 21:17 ` Jean-Pierre Schwickerath
2003-02-06 13:57 ` Derek Broughton
[not found] ` <008601c2cde7$ae63a2e0$3746028e-dP0OE4Ef7fWw5LPnMra/2Q@public.gmane.org>
2003-02-06 16:22 ` Ducrot Bruno
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='016901c2cd56$d2ee4f70$3746028e@bio.dfo.ca' \
--to=dbroughton-f3m4/jxepmf3fq9qlvqp4q@public.gmane.org \
--cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.