From: Antonio Ospite <ospite@studenti.unina.it>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, linux-input@vger.kernel.org,
Alan Ott <alan@signal11.us>
Subject: Re: ID_SERIAL for udev bluetooth joystick events
Date: Tue, 8 Feb 2011 12:05:33 +0100 [thread overview]
Message-ID: <20110208120533.12613888.ospite@studenti.unina.it> (raw)
In-Reply-To: <20110208074842.GC865@core.coreip.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On Mon, 7 Feb 2011 23:48:42 -0800
Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> On Fri, Feb 04, 2011 at 11:34:27PM +0100, Antonio Ospite wrote:
> > 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.
> >
[...]
> 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?
Regards,
Antonio
--
Antonio Ospite
http://ao2.it
PGP public key ID: 0x4553B001
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-02-08 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 22:34 ID_SERIAL for udev bluetooth joystick events Antonio Ospite
2011-02-08 7:48 ` Dmitry Torokhov
2011-02-08 11:05 ` Antonio Ospite [this message]
2011-02-08 17:08 ` Dmitry Torokhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110208120533.12613888.ospite@studenti.unina.it \
--to=ospite@studenti.unina.it \
--cc=alan@signal11.us \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox