From: Takashi Iwai <tiwai@suse.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Oliver Neukum <oneukum@suse.de>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] ACPI: Blacklist Win8 OSI for some HP laptop 2013 models
Date: Tue, 14 Jan 2014 17:33:50 +0100 [thread overview]
Message-ID: <s5hvbxmtte9.wl%tiwai@suse.de> (raw)
In-Reply-To: <20140114161244.GD4307@srcf.ucam.org>
At Tue, 14 Jan 2014 16:12:44 +0000,
Matthew Garrett wrote:
>
> On Mon, Jan 13, 2014 at 12:14:18PM +0100, Takashi Iwai wrote:
> > The BIOS on recent HP laptops behaves differently with Win8 OSI,
> > e.g. no backlight control and no rfkill are available. List them in
> > the blacklist as a workaround.
>
> What's the plan for fixing this properly?
For the backlight, there have been attempts to fix (use the native
backlight control primarily over ACPI), but didn't land to the
mainline yet.
For the rfkill part, it depends on the user-space. Without the patch,
it sends a scan code, and OS is supposed to do rfkill via each
driver. The proper key mapping would be needed. Not sure about the
LED state on the WiFi button, though, whether it's properly controlled
by WiFi and/or BT driver. With the patch, all rfkill and LED are
handled by BIOS, so it works as is.
Also I thought there are changes in some media keys by acpi_osi, but I
need to double check.
Takashi
next prev parent reply other threads:[~2014-01-14 16:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 11:14 [PATCH RESEND] ACPI: Blacklist Win8 OSI for some HP laptop 2013 models Takashi Iwai
2014-01-13 11:46 ` Rafael J. Wysocki
2014-01-13 11:33 ` Takashi Iwai
2014-01-14 16:12 ` Matthew Garrett
2014-01-14 16:33 ` Takashi Iwai [this message]
2014-01-14 16:36 ` Matthew Garrett
2014-01-14 16:43 ` Takashi Iwai
2014-01-14 16:44 ` Matthew Garrett
2014-01-14 16:42 ` Rafael J. Wysocki
2014-01-14 16:34 ` Matthew Garrett
2014-01-14 16:53 ` Rafael J. Wysocki
2014-01-14 16:42 ` 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=s5hvbxmtte9.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=oneukum@suse.de \
--cc=rjw@rjwysocki.net \
/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