Hi Bastien,

On Mon, Sep 10, 2012 at 4:58 PM, Luiz Augusto von Dentz
[off-list ref] wrote:

Hi Bastien,

On Mon, Sep 10, 2012 at 4:47 PM, Bastien Nocera [off-list ref] wrote:

quoted

Em Mon, 2012-09-10 às 16:11 +0300, Luiz Augusto von Dentz escreveu:

quoted

Hi David, Bastien,

So we are plannin to rid of the fakehid.c in favor of implementing it
properly inside the kernel similarly to what was done to wiimote, so
is there any obstacle for doing that?

The kernel seems to already have some support for sixaxis in
drivers/hid/hid-sony.c, so I suppose the following would enable us to
use it:

It won't. They're not the same hardware.

What hardware is that then? And why wouldn't the kernel be able to
support even if it is a different driver?

So what exactly are the difference between 0x0268 and 0x0306? And why
sixpair.c save as 0x0268 while fakeinput.c uses 0x0306?

Also, after fixing sixpair.c to be able to compile it does add to the
storage but it does not create any object until bluetoothd is
restarted and even after restart it does not allow the device to
connect because it does has the record (although this can be fixed by
automatically add the UUID once we find out it is attempt to connect).

-- 
Luiz Augusto von Dentz