From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [PATCH v2 4/4] toshiba_acpi: Add blacklist for models with hotkey problems Date: Thu, 5 Jan 2012 19:34:31 +0000 Message-ID: <20120105193431.GA26097@srcf.ucam.org> References: <1325617358-8286-1-git-send-email-seth.forshee@canonical.com> <1325617358-8286-5-git-send-email-seth.forshee@canonical.com> <20120105182627.GE24242@srcf.ucam.org> <20120105193228.GB25386@ubuntu-macmini> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20120105193228.GB25386@ubuntu-macmini> Sender: platform-driver-x86-owner@vger.kernel.org To: Len Brown , Azael Avalos , Thomas Renninger , platform-driver-x86@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-acpi@vger.kernel.org On Thu, Jan 05, 2012 at 01:32:28PM -0600, Seth Forshee wrote: > Also a side note of interest: The machines that suffer from this all > also have a WMI interface with code to support hotkeys, and that code > shouldn't suffer from this problem. Unfortunately these models are the > only ones I've seen with this WMI interface, and the code to generate > the hotkey events isn't executed if the OS reports itself as Vista or > newer. In that case, can you check for the presence of the WMI interface and then refuse to bind? That's seem far simpler than adding an unknown number of systems to the blacklist. -- Matthew Garrett | mjg59@srcf.ucam.org