Re: [Libusb-win32-devel] lots of bugs (Carl Kenner)

[Xiaofan C. <xia...@gm...>]

On 8/14/07, Carl Kenner <car...@gm...> wrote:
> I can't use HID as a backend, because the windows HID isn't working.
> Presumably because the SIXAXIS uses a malformed HID descriptor, and it
> won't let me read this feature report. I'm reasonably confident the
> device isn't a keyboard or mouse, it seems to just be a HID joystick
> or gamepad. Reading the same feature report with libusb is easy. Once
> I have read this feature report, the device will start sending input
> reports to the computer, but before that it won't.
>
> Now all the other sixaxis drivers for windows use the libusb filter
> driver to read this one feature report, while windows still sees it as
> a gamepad. So it must work on some computers. But it doesn't work on
> the computers I tested it on.

I see. So it is a gamepad.

Now I understand why your interrupt transfer will not work.
You do need to claim the interface (use the device driver, set the
configuration, claim the interface) in order for the interrupt transfer
to work. You can try this.

You do not need to claim the interface to get control transfer to work.
Therefore you can use the filter driver. If I am not wrong, you do not
need to (and probably you can not) set configuration since the
HID driver has already done that and claim the interface. I am not
100% sure here though. You can try this.

Google found this and maybe you can give it a try.
http://www.bricklife.com/library/sixaxis-init.c


Regards,
Xiaofan




Regards,
Xiaofan