From: <derek.philip@tesco.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and bluetooth devices
Date: Mon, 08 Nov 2004 15:44:22 +0000 [thread overview]
Message-ID: <20041108154422.EUWV25413.dircache05-winn.mailhost.ntl.com@localhost> (raw)
Hi Marcel
Thanks for your reply.
I would just like to make my situation a little clearer.
My reason for creating a persistent link is that I have at
least 8 USB Bluetooth dongles under test. the scripts I
use may restart them in a random order and I run the
chance of reconnecting to the wrong deive if I use say
hci0.
I'm not sure what you mean by use the BD_ADDR!
I currently use CSrs btcli hci tool for communicating to
the device.
I read in one of the udev howtos that it is possible to
rename the Ethernet interfaces, eth0, with a rule in udev.
Is it possible to do the same with hci0, Bluetooth
interfaces.
Thanks
Derek
>
> Hi Derek,
>
> > I was trying to write a rule to provide a persistent
naming for multiple
> > USB Bluetoot dongles. I need this for testing
purposes, as the devices
> > may be restarted at random times and I need to ensure
I'm speaking to
> > the same device.
> >
> > My attempts so far have failed!
> >
> > I have the following output from udevinfo -a
-p /sys/class/bluetooth/hci0
> >
> > looking at the device chain at
> > '/sys/devices/pci0000:00/0000:00:1d.2/usb2/2-1':
> > BUS="usb"
> > ID="2-1"
> > SYSFS{bConfigurationValue}="1"
> > SYSFS{bDeviceClass}="e0"
> > SYSFS{bDeviceProtocol}="01"
> > SYSFS{bDeviceSubClass}="01"
> > SYSFS{bMaxPower}="200mA"
> > SYSFS{bNumConfigurations}="1"
> > SYSFS{bNumInterfaces}=" 3"
> > SYSFS{bcdDevice}="1393"
> > SYSFS{bmAttributes}="80"
> > SYSFS{detach_state}="0"
> > SYSFS{devnum}="4"
> > SYSFS{idProduct}="0001"
> > SYSFS{idVendor}="0a12"
> > SYSFS{manufacturer}="Cambridge Silicon Radio"
> > SYSFS{maxchild}="0"
> > SYSFS{product}="CSR NanoSira"
> > SYSFS{serial}="012C5A-5B-0002"
> > SYSFS{speed}="12"
> > SYSFS{version}=" 2.00"
> >
> >
> > I was thinking that my rule would be
> >
> > BUS="usb", SYSFS{serial}="012C5A-5B-0002", name=%k
SYMLINK="Nano%n"
> >
> > This has no affect!
>
> Bluetooth devices don't use any device nodes. You can
identify them by
> their BD_ADDR.
>
> Regards
>
> Marcel
>
>
>
>
>
> --__--__--
>
> _______________________________________________
> Linux-hotplug-devel mailing list
> Linux-hotplug-devel@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
>
>
> End of Linux-hotplug-devel Digest
>
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-11-08 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 15:44 derek.philip [this message]
2004-11-09 7:20 ` udev and bluetooth devices Marcel Holtmann
2004-11-10 2:29 ` Marcel Holtmann
2004-11-12 1:55 ` Marcel Holtmann
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=20041108154422.EUWV25413.dircache05-winn.mailhost.ntl.com@localhost \
--to=derek.philip@tesco.net \
--cc=linux-hotplug@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