From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [PATCH] ACPI video: Add video_switch_key option Date: Wed, 24 Nov 2010 14:42:39 +0000 Message-ID: <20101124144239.GA31411@srcf.ucam.org> References: <20101124142618.GB30831@srcf.ucam.org> <20101124143517.GA31182@srcf.ucam.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([93.93.128.6]:37956 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751342Ab0KXOmo (ORCPT ); Wed, 24 Nov 2010 09:42:44 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Takashi Iwai Cc: Len Brown , linux-acpi@vger.kernel.org On Wed, Nov 24, 2010 at 03:38:05PM +0100, Takashi Iwai wrote: > Unfortunately, this is the standard behavior on most desktops :-< > Fn-F4 (or whatever) media key produces this exact key code, and the > desktops (including Windows) expect this behavior. Hm. Ok, let's make sure that we're doing this right. There's several different notifications which can generate the same keycode (ACPI_VIDEO_NOTIFY_SWITCH, ACPI_VIDEO_NOTIFY_PROBE and ACPI_VIDEO_NOTIFY_CYCLE) - which of them's actually being triggered here? -- Matthew Garrett | mjg59@srcf.ucam.org