[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200710282238.11692.dtor@insightbb.com>
Date: Sun, 28 Oct 2007 22:38:10 -0400
From: Dmitry Torokhov <dtor@...ightbb.com>
To: linux-input@...ey.karlin.mff.cuni.cz
Cc: Jiri Kosina <jikos@...os.cz>,
Torsten Kaiser <just.for.lkml@...glemail.com>,
Adrian Bunk <bunk@...nel.org>,
Nick Sillik <n.sillik@...ple.edu>,
David Brownell <david-b@...bell.net>,
Greg Kroah-Hartman <gregkh@...e.de>,
linux-kernel@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net
Subject: Re: [RFC: 2.6 patch] remove the USB_STORAGE_ONETOUCH driver
On Sunday 28 October 2007 16:39, Jiri Kosina wrote:
> On Sun, 28 Oct 2007, Torsten Kaiser wrote:
>
> > But it looks like that uses another driver:
> > hiddev0hidraw1: USB HID v1.10 Device [Western Digital External HDD] on
> > usb-0000:00:02.1-5.2
> > Otherwise I would be willing to try to test this, if someone would tell
> > me how to check that the second commit did fix the suspend problem.
>
> If you need to unbind usbhid driver from the device and bind another one,
> you can use the 'unbind' and 'bind' files in sysfs.
>
> As soon as the driver you are willing to test is bound to the device, you
> can go ahead with testing any functionality you wish (probably
> suspend/resume cycle is needed here?).
>
> If the device is claimed by usbhid driver (because its descriptor probably
> states that it's HID-compliant device) and should be claimed by another
> driver, it's necessary to add it to usbhid blacklist -- just let me know.
>
Maybe onetouch driver is not needed after all. I wonder what key/button does
HID deriver reports when it binds to it... Torsten, could you please post
your /proc/bus/input/devices?
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists