From: Yves-Alexis Perez <corsac@debian.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Borislav Petkov <bp@alien8.de>,
ibm-acpi-devel@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [ibm-acpi-devel] x230: unhandled HKEY event 0x6050
Date: Sat, 09 Mar 2013 09:06:46 +0100 [thread overview]
Message-ID: <1362816406.19016.16.camel@scapa> (raw)
In-Reply-To: <20130307003016.GA21655@khazad-dum.debian.net>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
On mer., 2013-03-06 at 21:30 -0300, Henrique de Moraes Holschuh wrote:
> On Mon, 04 Mar 2013, Borislav Petkov wrote:
> > I get this in dmesg with 3.9-rc1:
> >
> > [ 12.951434] thinkpad_acpi: unhandled HKEY event 0x6050
> > [ 12.951438] thinkpad_acpi: please report the conditions when this
> event happened to ibm-acpi-devel@lists.sourceforge.net
> > [ 13.516752] thinkpad_acpi: unknown possible thermal alarm or
> keyboard event received
> >
> > when pressing Fn+F8/F9, i.e. the display backlight keys. I'm loading
> > thinkpad_acpi with brightness_enable=1 and booting the kernel with
> > "acpi_backlight=vendor" so that the backlight intensity gets
> controlled
> > by thinkpad_acpi. But the last maybe shouldn't complain about it,
> no?
>
> It shouldn't even work right on a x230, that box should be doing
> standard
> ACPI backlight control...
Also see https://bugzilla.kernel.org/show_bug.cgi?id=51231 and
https://patchwork.kernel.org/patch/2124861/
Regards,
--
Yves-Alexis
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-03-09 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 21:38 x230: unhandled HKEY event 0x6050 Borislav Petkov
2013-03-07 0:30 ` Henrique de Moraes Holschuh
2013-03-07 8:43 ` Borislav Petkov
2013-03-09 8:06 ` Yves-Alexis Perez [this message]
2013-03-09 11:36 ` [ibm-acpi-devel] " Borislav Petkov
2013-03-09 20:49 ` Henrique de Moraes Holschuh
2013-03-09 22:13 ` Borislav Petkov
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=1362816406.19016.16.camel@scapa \
--to=corsac@debian.org \
--cc=bp@alien8.de \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@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 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.