public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	Thomas Renninger <trenn@suse.de>, Len Brown <lenb@kernel.org>,
	linux-acpi <linux-acpi@vger.kernel.org>,
	"Starikovskiy, Alexey Y" <aystarik@gmail.com>
Subject: Re: Kernel Version specific vendor override possibilities needed - Revert and provide osi=linux or provide a replacement
Date: Thu, 21 Feb 2008 14:30:52 +0000	[thread overview]
Message-ID: <20080221143052.GA8389@srcf.ucam.org> (raw)
In-Reply-To: <20080221135132.GE14614@mit.edu>

On Thu, Feb 21, 2008 at 08:51:32AM -0500, Theodore Tso wrote:

> It would be much better if we define feature-specific OSI() strings
> that have well defined meanings for each place where Lenovo has to do
> something different than What Happens With Windows --- especially for
> stuff which is generic, since all laptop manufactuers need to
> interoperate with whatever cr*p Windows ship.  At the end of the day,
> since Intel was originally too lazy to ship an ACPI conformance test
> suite, like it or not, Windows *has* become the APCI conformance test
> suite, and all laptop manufacturers (at least for today) must bow to
> the might and power which is the market share of Microsoft.

My concern with this is that until we know where we deviate from the 
Windows behaviour, we don't know what strings we'd need to provide. And 
once we *do* know where we deviate, we should fix that deviation rather 
than provide an identifying string.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2008-02-21 14:31 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20  1:44 Kernel Version specific vendor override possibilities needed - Revert and provide osi=linux or provide a replacement Thomas Renninger
2008-02-20 10:31 ` Tomas Carnecky
2008-02-20 13:14   ` Henrique de Moraes Holschuh
2008-02-20 15:31   ` Thomas Renninger
2008-02-20 17:32 ` Matthew Garrett
2008-02-20 18:21   ` Thomas Renninger
2008-02-20 18:46     ` Matthew Garrett
2008-02-20 18:23   ` Henrique de Moraes Holschuh
2008-02-20 18:49     ` Matthew Garrett
2008-02-21  3:13       ` Henrique de Moraes Holschuh
2008-02-21  5:31         ` Sergio Monteiro Basto
2008-02-21 15:55           ` Henrique de Moraes Holschuh
2008-02-21  9:15         ` Matthew Garrett
2008-02-21 13:51           ` Theodore Tso
2008-02-21 14:30             ` Matthew Garrett [this message]
2008-02-21 14:48               ` Alexey Starikovskiy
2008-02-21 14:55                 ` Matthew Garrett
2008-02-21 15:07                   ` Alexey Starikovskiy
2008-02-21 15:50               ` Henrique de Moraes Holschuh
2008-02-26 16:26             ` Thomas Renninger
2008-02-26 16:31               ` Matthew Garrett
2008-02-22 14:07   ` Thomas Renninger
2008-02-22 18:10     ` Matthew Garrett
2008-02-26 16:26       ` Thomas Renninger
2008-02-21  8:41 ` Len Brown
2008-02-21 15:41   ` Thomas Renninger
2008-02-21 15:58     ` Matthew Garrett
2008-02-21 17:15     ` Theodore Tso
2008-02-22 23:36       ` Len Brown
2008-02-23  0:06     ` 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=20080221143052.GA8389@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=aystarik@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=trenn@suse.de \
    --cc=tytso@MIT.EDU \
    /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