From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Matthias Heinz <mheinz@cs.uni-frankfurt.de>
Cc: linux-acpi@vger.kernel.org
Subject: Re: samsung x360, acpi support
Date: Sat, 6 Dec 2008 11:43:58 +0000 [thread overview]
Message-ID: <20081206114358.GA4821@srcf.ucam.org> (raw)
In-Reply-To: <200812041915.39971.mheinz@cs.uni-frankfurt.de>
On Thu, Dec 04, 2008 at 07:15:39PM +0100, Matthias Heinz wrote:
> 1) Backlight support: I cant control the brightness of the backlight with a
> 2.6.28-rc7. It worked under mysterious circumstances with a 2.6.26.
> Mysterious, because i had to use /proc/acpi/video/NVID/LCD/brightness to set
> it, which obviously belongs to a nvidia driver (but theres nothing from
> nvidia in there...)
Do you have the i915 module loaded? NVID is simply the vendor's name for
the ACPI object representing the video controller.
> 2) Wifi LED: I dont know if this is a wifi driver issue or has to be
> controlled by acpi.
There's no standardised way for controlling LEDs via ACPI, so it's
probably a wifi driver issue.
> 3) The keyboard is not sending acpi events for several switches. It sends
> (unknown) keycodes that have to be interpreted by the OS.
> But there seems to be an option to change between acpi events and key events,
> because i can control the backlight when grub is running and in the early
> boot phase of the kernel. I dont know if this should be classified as
> problem, but because X is catching all key events handling the wlan power
> function is a problem of the actual user.
The brightness keys will be trapped by the BIOS and brightness change
code run in system management mode before ACPI is enabled, which only
happens part-way through the Linux boot process. So it's normal for the
behaviour to change at that point. It's also not unusual for hotkeys to
be sent via the ekyboard - ACPI doesn't have any specified way for
handling generic hotkeys other than the sleep and power buttons.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-12-06 11:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 18:15 samsung x360, acpi support Matthias Heinz
2008-12-05 1:05 ` Zhang Rui
2008-12-05 19:36 ` Matthias Heinz
2008-12-05 19:50 ` Matthias Heinz
2008-12-06 11:43 ` Matthew Garrett [this message]
2008-12-06 13:26 ` Matthias Heinz
2008-12-06 16:26 ` Matthew Garrett
2008-12-06 16:33 ` Matthias Heinz
2008-12-06 16:42 ` Matthew Garrett
2008-12-06 17:28 ` Matthias Heinz
2008-12-06 17:32 ` Matthew Garrett
2008-12-06 18:47 ` Matthias Heinz
2008-12-06 18:54 ` Matthew Garrett
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=20081206114358.GA4821@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mheinz@cs.uni-frankfurt.de \
/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