public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Andi Kleen <ak@linux.intel.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI: Provide a spec conform OSI interface to the BIOS
Date: Fri, 18 Jul 2008 19:22:11 +0200	[thread overview]
Message-ID: <200807181922.11728.trenn@suse.de> (raw)
In-Reply-To: <48804349.607@linux.intel.com>

On Friday 18 July 2008 09:16:25 am Andi Kleen wrote:
> Thomas Renninger wrote:
> > Introduce acpi_osi=windows_false boot parameter
> > Introduce CONFIG_ACPI_OSI_SPEC_CONFORM config option
>
> Why are you adding the CONFIG option? 
> In what circumstances would one 
> set it? If anything I think this should be a boot option only for now.
E.g. for OEMs that do not need to support all BIOSes in the world who 
can just check for the config option and then know it behaves as written in 
the spec and being able to support Linux and Windows through the same BIOS.

But you are right, the compile option only makes sense if acpi_osi="Windows 
2006" can be used to simulate a specific Windows OS via boot param, which is 
not the case.

But I want the boot param. This one makes very much sense to test BIOSes 
whether they stick to the ACPI spec and work fine on Linux without Windows 
simulation. Is that ok?

> Probably needs more discussion first.
I always wanted to write down the arguments again, but this takes a lot time.
Will you accept the boot param only?

       Thomas

  reply	other threads:[~2008-07-18 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 17:37 [PATCH] ACPI: Provide a spec conform OSI interface to the BIOS Thomas Renninger
2008-07-18  7:16 ` Andi Kleen
2008-07-18 17:22   ` Thomas Renninger [this message]
2008-07-20  2:27     ` Len Brown
2008-07-24 15:27       ` Thomas Renninger

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=200807181922.11728.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=ak@linux.intel.com \
    --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