From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Thomas Renninger <trenn@suse.de>, Len Brown <lenb@kernel.org>,
linux-acpi <linux-acpi@vger.kernel.org>,
Theodore Tso <tytso@MIT.EDU>,
"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 05:31:53 +0000 [thread overview]
Message-ID: <1203571913.3764.19.camel@localhost.localdomain> (raw)
In-Reply-To: <20080221031324.GB6344@khazad-dum.debian.net>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
On Thu, 2008-02-21 at 00:13 -0300, Henrique de Moraes Holschuh wrote:
> On Wed, 20 Feb 2008, Matthew Garrett wrote:
> > It doesn't punish them. They're the ones who are going to work with us
> > to ensure that Linux works on their hardware, and their needs are going
>
> And since when we have to work exactly like Windows (whatever version) does
> in THAT case?
>
> Also, why would one thing (proper replacement for OSI(Linux)) cause any sort
> of difference over the other (trying to be bug-to-bug compatible with
> Microsoft crap).
>
I agree with Henrique. Since we have, in fact, more Windows cases than
Linux cases and for Linux, just announce that is recommended,
osi=linux.
Also it is possible put Linuxs bios in a kind of white-list in kernel
code ...
--
Sérgio M. B.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2192 bytes --]
next prev parent reply other threads:[~2008-02-21 5: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 [this message]
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
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=1203571913.3764.19.camel@localhost.localdomain \
--to=sergio@sergiomb.no-ip.org \
--cc=aystarik@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.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