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] [day] [month] [year] [list]

Date:	Tue, 14 Jan 2014 16:44:57 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Takashi Iwai <tiwai@...e.de>
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

On Tue, Jan 14, 2014 at 05:43:56PM +0100, Takashi Iwai wrote:
> At Tue, 14 Jan 2014 16:36:00 +0000,
> Matthew Garrett wrote:
> > 
> > On Tue, Jan 14, 2014 at 05:33:50PM +0100, Takashi Iwai wrote:
> > 
> > > 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.
> > 
> > Ok, so userspace needs to work - there's plenty of hardware that only 
> > sends a scancode already. Let's just add the keycode and then remove 
> > this once the backlight stuff is fixed.
> 
> Yes, sounds feasible.

Oh, and once we've got the keycode in it's possible to handle this 
in-kernel - you just need rfkill-input.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/