Re: hiddev and input devices (PS3 sixaxis)

On Wed, 2007-11-28 at 16:09 +0100, Jiri Kosina wrote:
> On Wed, 28 Nov 2007, Bastien Nocera wrote:
> 
> > #define HID_QUIRK_HIDDEV                        0x00000010
> > #define HID_QUIRK_SONY_PS3_CONTROLLER           0x00040000
> > #define USB_VENDOR_ID_SONY                      0x054c
> > #define USB_DEVICE_ID_SONY_PS3_CONTROLLER       0x0268
> > So, that would mean:
> > usbhid.quirks=0x054c:0x0268:0x00040010
> 
> Hi,
> 
> yes, these two are functionally equivalent.
> 
> > I've attached a simple patch to make it create the hiddev for the 
> > sixaxis.
> 
> What is this needed for? If you are intending this for mainline, I'll need 
> proper changelog (explaining why it is needed) and Signed-off-by line.

Sorry, git hates me, but you can use my one-liner however you want ;)

The goal is to have a udev callout when the joypad is plugged in, so
that it "pairs" for Bluetooth usage with the machine it's being plugged
in.

The device is not discoverable, and needs to be poked (as the original I
sent does) to set its master (ie. which Bluetooth device it will try to
connect to when the "Home" button is pressed without a cable plugged
in).

Using libusb means disconnecting the device from its driver to get the
report descriptor. Using hiddev, we can poke it without relinquishing
control over it, so when you plug it in, it would still work as a pad.

Cheers


-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel