All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alan Jenkins <sourcejedi.lkml@googlemail.com>
Cc: Chris Bagwell <chris@cnpbagwell.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	acpi4asus-user@lists.sourceforge.net,
	platform-driver-x86@vger.kernel.org
Subject: Re: [Acpi4asus-user] 1005PE's and backlight controls
Date: Wed, 14 Apr 2010 17:40:30 +0100	[thread overview]
Message-ID: <20100414164030.GA14758@srcf.ucam.org> (raw)
In-Reply-To: <t2i9b2b86521004140923x9c1aaa64p867674329ae158af@mail.gmail.com>

On Wed, Apr 14, 2010 at 05:23:22PM +0100, Alan Jenkins wrote:

> I suggest you contact the ACPI video maintainer, Zhang Rui
> <rui.zhang@intel.com>, and attach the output of "dmidecode".  The best
> way would probably be to report the problem on bugzilla.kernel.org (on
> the ACPI video driver).
> 
> I think it will indeed be possible to blacklist your machine, because
> someone has already anticipated this problem :-).

dmi blacklisting is almost certainly wrong. It's more likely that 
eeepc-laptop shouldn't be registering a backlight if 
acpi_video_backlight_support() is true, but we'll then want to 
investigate whether we also need to send the keyboard events through.

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

  reply	other threads:[~2010-04-14 16:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <y2g3b2dfeb01004131934x67e23d80vc73dfd6d5af133fa@mail.gmail.com>
     [not found] ` <o2z71cd59b01004132316jd06b2a40m593ee5376e4dfa28@mail.gmail.com>
     [not found]   ` <r2odb599ead1004140624g56c2465qc4aaa3d1ee1c79b3@mail.gmail.com>
2010-04-14 13:45     ` [Acpi4asus-user] 1005PE's and backlight controls Corentin Chary
2010-04-14 14:00       ` Chris Bagwell
2010-04-15  3:34         ` Wang, Yong Y
2010-04-15  4:35           ` Wang, Yong Y
     [not found] ` <y2g3b2dfeb01004131934x67e23d80vc73dfd6d5af133fa-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-14 16:23   ` Alan Jenkins
2010-04-14 16:40     ` Matthew Garrett [this message]
2010-04-14 17:14       ` [Acpi4asus-user] " Chris Bagwell
2010-04-14 17:26         ` Matthew Garrett
2010-04-14 22:18           ` Chris Bagwell
2010-04-15  1:30             ` Zhang Rui
2010-04-15  1:42               ` Zhang Rui
2010-04-15  2:10                 ` [Acpi4asus-user] " Chris Bagwell
2010-04-15  2:29                   ` Zhang Rui
2010-04-16  0:02                     ` Chris Bagwell
2010-04-15  2:00               ` Chris Bagwell
2010-04-14 20:07       ` 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=20100414164030.GA14758@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=chris@cnpbagwell.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.