Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755452Ab1EFM6S (ORCPT ); Fri, 6 May 2011 08:58:18 -0400 Received: from cantor.suse.de ([195.135.220.2]:60809 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754872Ab1EFM6R (ORCPT ); Fri, 6 May 2011 08:58:17 -0400 Date: Fri, 6 May 2011 14:58:12 +0200 (CEST) From: Jiri Kosina To: Alan Stern , "Adi J. Sieker" Cc: Oliver Neukum , USB list , linux-input@vger.kernel.org, Kernel development list Subject: Re: USB keyboard recognized as HID keyboard but doesn't work In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1165 Lines: 39 On Tue, 3 May 2011, Alan Stern wrote: > > Do you know of a way for me to tell the kernel/usbhid to use interface 1 > > and ignore interface 0? > > Well, you can always unbind interface 0 from usbhid -- it corresponds > to the 2-1.1:1.0 file in /sys/bus/usb/drivers/usbhid/. If you do that, > you'll probably find the few keys which _do_ currently work suddenly > stop working. > > But there's nothing to be done immediately about interface 1; usbhid is > _already_ using it. It just isn't using it correctly. Adi, could you please provide output of cat /syse/kernel/debug/hid//rdesc anytime after the keyboard has been plugged, and cat /syse/kernel/debug/hid//events from the time you press any of the working and non-working keys? (both cases will be interesting). Oh, and the above assumes that you have debugfs mounted under /sys/kernel/debug. Thanks, -- Jiri Kosina SUSE Labs -- 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/