-----Original Message----- From: Greg KH <[EMAIL PROTECTED]> To: Keenan Wilkie <[EMAIL PROTECTED]> Date: Wed, 20 Jun 2001 08:21:13 -0700 Subject: Re: [Linux-usb-users] PSX/N64 Gamepad Adaptor (supposedly HID compliant) > On Tue, Jun 19, 2001 at 11:21:48PM -0400, Keenan Wilkie wrote: > > I used usbview to see if anything was being detected at all and it > listed > > the device as 'Unknown Device' in red text (I wish the utility had > better > > documention -- and that I knew what I was doing), though it is > detected as > > a HID class device. > > Patches for documentation are gladly accepted :) Like I'm smart enough to know what that means :) > usbview shows "Unknown Device" as the device does not have any strings > in it to describe itself and it isn't a keyboard or mouse. > > It shows up as red because no driver is bound to it. Have you loaded > the hid and joydev modules? I'd guessed as much about the reason for itself IDd as 'Unknown Device' (in fact I did a cat /proc/bus/usb/devices > /tmp/devices and editied it to confirm such). However, I'm not sure why a device that is identified as HID wouldn't be bound do the hid driver. I do modprobe uhci, joydev and hid. Input is already in the kernel (slight oversight on my part, but that shouldn't affect anything, right?) and I have also tried a different kernel configuration where all of the drivers were compiled directly into the kernel with no different results. I did notice that if I move the device to a different USB port I have to modprobe hid again before it will work (er, show up in the listed devices under usbview) -- is that normal? Is there any way I can force the hid driver to bind itself to the device? _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: http://lists.sourceforge.net/lists/listinfo/linux-usb-users
