From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Len Brown <lenb@kernel.org>, linux acpi <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] acpi/blacklist: enable OSI(Linux) on newer eeepc
Date: Sat, 21 Nov 2009 23:28:15 +0000 [thread overview]
Message-ID: <20091121232815.GA17749@srcf.ucam.org> (raw)
In-Reply-To: <71cd59b00911211322t45be6c92g2a0c78c03d7eb5e9@mail.gmail.com>
On Sat, Nov 21, 2009 at 10:22:45PM +0100, Corentin Chary wrote:
> I think we could add that patch to 2.6.32, then revert it in 2.6.33 (or later)
> when a eeepc-wmi driver (or wmi support inside eeepc-laptop) is available.
> And I don't think such a driver (patch) will be available before 2.6.32.
>
> That means that owner of 1000h and 1005ha won't be able to use eeepc-laptop
> (camera, rfkill, hotkeys) without adding acpi_osi="Linux" manually in 2.6.32.
>
> I know this is not a long term solution.
The reason I'm not keen is that hardware vendors seem to continue
believing that Linux claims to be Linux - it's almost understandable for
Asus when they're shipping 2.6.remotely_exploitable on their hardware,
but Lenovo are still doing it for no obvious reason. I'm worried that
even doing a single release with this defined will result in Asus
pulling the same trick at some point in the future.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-11-21 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 21:29 [PATCH] acpi/blacklist: enable OSI(Linux) on newer eeepc Corentin Chary
2009-11-21 18:45 ` Matthew Garrett
2009-11-21 21:22 ` Corentin Chary
2009-11-21 23:28 ` Matthew Garrett [this message]
2009-11-23 16:24 ` Len Brown
2009-11-23 16:29 ` Matthew Garrett
2009-11-23 17:01 ` Corentin Chary
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=20091121232815.GA17749@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=corentin.chary@gmail.com \
--cc=lenb@kernel.org \
--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