linux-kernel - Re: [PATCH RESEND] ACPI: Blacklist Win8 OSI for some HP laptop 2013 models

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 14 Jan 2014 17:33:50 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Len Brown <lenb@...nel.org>, Oliver Neukum <oneukum@...e.de>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND] ACPI: Blacklist Win8 OSI for some HP laptop 2013 models

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/