Date: Tue, 14 Jan 2014 17:43:56 +0100
Message-ID: <s5hsisqtsxf.wl%tiwai@suse.de>
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
In-Reply-To: <20140114163600.GB6649@srcf.ucam.org>
References: <1389611658-19424-1-git-send-email-tiwai@suse.de>
	<20140114161244.GD4307@srcf.ucam.org>
	<s5hvbxmtte9.wl%tiwai@suse.de>
	<20140114163600.GB6649@srcf.ucam.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.3
 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org

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.


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