From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [PATCH RESEND] ACPI: Blacklist Win8 OSI for some HP laptop 2013 models Date: Tue, 14 Jan 2014 16:44:57 +0000 Message-ID: <20140114164457.GA8166@srcf.ucam.org> References: <1389611658-19424-1-git-send-email-tiwai@suse.de> <20140114161244.GD4307@srcf.ucam.org> <20140114163600.GB6649@srcf.ucam.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Takashi Iwai Cc: "Rafael J. Wysocki" , Len Brown , Oliver Neukum , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-acpi@vger.kernel.org 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@srcf.ucam.org