Re: ID_SERIAL for udev bluetooth joystick events

On Tue, Feb 08, 2011 at 12:05:33PM +0100, Antonio Ospite wrote:

On Mon, 7 Feb 2011 23:48:42 -0800
Dmitry Torokhov [off-list ref] wrote:

quoted

On Fri, Feb 04, 2011 at 11:34:27PM +0100, Antonio Ospite wrote:

quoted

Hi,

I have a question about udev events generated by a bluetooth joystick:
when the bt joystick generates the joystick event, the ID_SERIAL
property matches the one of the bt adapter not the one of the joystick.

For example (using "udevadm monitor --property"), when connecting the
Sony Sixaxis via usb I get:
ID_SERIAL=Sony_PLAYSTATION_R_3_Controller
in the input and joystick events, but when I connect it via bt, I get:
ID_SERIAL=Broadcom_Corp_ANYCOM_Blue_USB-200_250
which matches my bluetooth adapter.

[...]

quoted

This should be directed to udev list as composition of ID_SERIAL is
done exclusively by udev. It looks like it scans parent till it finds
first USB device (thus skipping all BT-specific data).

Thanks Dmitry, I'll resend this to linux-hotplug.

Is it OK for cases like this to still keep linux-bluetooth and
linux-input in CC?

Sure, why not.

-- 
Dmitry