From: Corentin Chary <corentin.chary@gmail.com>
To: Alan Jenkins <sourcejedi.lkml@googlemail.com>
Cc: Richard Hughes <hughsient@gmail.com>,
gnome-power-manager-list@gnome.org,
acpi4asus-user@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Darren Salt <linux@youmustbejoking.demon.co.uk>
Subject: Re: [gpm] [PATCH 2.6.29] eeepc-laptop: report brightness control events via the input layer
Date: Fri, 19 Jun 2009 00:44:28 +0200 [thread overview]
Message-ID: <71cd59b00906181544j4fa957b1n6dcd3bdf34efc423@mail.gmail.com> (raw)
In-Reply-To: <9b2b86520906180633i2bc2ad6bk20c43d8426798b18@mail.gmail.com>
On Thu, Jun 18, 2009 at 3:33 PM, Alan
Jenkins<sourcejedi.lkml@googlemail.com> wrote:
> On 6/16/09, Richard Hughes <hughsient@gmail.com> wrote:
>> On Tue, Jun 16, 2009 at 10:44 AM, Corentin
>> Chary<corentin.chary@gmail.com> wrote:
>>> Ok, so we just need to patch this file :
>>> http://cgit.freedesktop.org/hal-info/tree/fdi/information/10freedesktop/10-laptop-panel-hardware.fdi
>>
>> Yes
>>
>>> But I'm not sure how to do it to make it works on all Eeepc.
>>
>> Well, really we want to match "classes of eeepc", so matching with
>> prefix might be a good idea.
>>
>> Richard.
>
> Yes please! I see the 701 is (just added?) on the list, but this
The 701 was already here when I checked.
> But I hope there's a nicer solution. Corentin, do you think it would
> be correct to apply this quirk to _all_ Asus laptops?
I can confirm that all the asus laptop I know change the brightness in the
firmware. So, in my opinion, we can safely apply this quirk to all Asus laptops.
--
Corentin Chary
http://xf.iksaif.net - http://uffs.org
prev parent reply other threads:[~2009-06-18 22:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 17:57 Darren Salt
2009-04-04 4:18 ` Matthew Garrett
2009-04-04 8:33 ` Corentin Chary
2009-04-04 12:20 ` Darren Salt
2009-04-04 12:35 ` Corentin Chary
2009-04-04 22:10 ` Darren Salt
2009-04-05 8:22 ` Corentin Chary
2009-06-08 15:24 ` Alan Jenkins
2009-06-13 8:55 ` Corentin Chary
2009-06-13 9:33 ` Alan Jenkins
2009-06-13 10:06 ` Corentin Chary
2009-06-13 12:55 ` Darren Salt
2009-06-13 17:51 ` Alan Jenkins
2009-06-14 19:26 ` Corentin Chary
2009-06-15 8:09 ` Alan Jenkins
2009-06-15 8:12 ` Alan Jenkins
2009-06-16 8:33 ` [gpm] " Richard Hughes
2009-06-16 8:34 ` Alan Jenkins
2009-06-16 8:47 ` Richard Hughes
2009-06-16 9:44 ` Corentin Chary
2009-06-16 10:04 ` Richard Hughes
2009-06-18 13:33 ` Alan Jenkins
2009-06-18 22:44 ` Corentin Chary [this message]
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=71cd59b00906181544j4fa957b1n6dcd3bdf34efc423@mail.gmail.com \
--to=corentin.chary@gmail.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=gnome-power-manager-list@gnome.org \
--cc=hughsient@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@youmustbejoking.demon.co.uk \
--cc=sourcejedi.lkml@googlemail.com \
/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
Powered by JetHome