From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: 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: Wed, 20 Feb 2008 18:49:54 +0000 [thread overview]
Message-ID: <20080220184954.GB23679@srcf.ucam.org> (raw)
In-Reply-To: <20080220182339.GC17648@khazad-dum.debian.net>
On Wed, Feb 20, 2008 at 03:23:40PM -0300, Henrique de Moraes Holschuh wrote:
> On Wed, 20 Feb 2008, Matthew Garrett wrote:
> > Let's look at this differently. Most hardware is produced by vendors who
> > don't care about Linux. We need to make that hardware work anyway. The
> > only way we can achieve that is to be bug-compatible with Windows.
> > Therefore, any way in which Linux behaviour varies from Windows
> > behaviour is a bug. The only reason to export any indication that the
> > kernel is Linux is because our behaviour is not identical to Windows.
> > But, given that that's a bug, the solution should be to fix Linux and
> > not to encourage vendors to put workarounds in their firmware.
>
> That punishes vendors which actually care about Linux. These are quite
> rare in the laptop and desktop market, but they do exist.
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
to be prioritised over those of vendors who don't care about Linux. The
other choice (encourage vendors to put workarounds in their firmware
instead) *does* punish users who've ended up with laptops that aren't
actively supported - like, say, pretty much anything on the market.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-02-20 18:50 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 [this message]
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
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=20080220184954.GB23679@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