You are not logged in.

#1 2015-03-18 23:50:42

yoooyle
Member
Registered: 2015-02-25
Posts: 2

Persistent mapping from BT hardware to hci name

I want a stable mapping from bluetooth hardware to hciX under /sys/class/bluetooth, similar to how wlanX maps to wifi chips.

I wrote a udev rule. The rule is matching correctly by vender/product. But how do i actually change the name? With wlan, i can simply specify NAME="wlan0". Thanks!

SUBSYSTEM="bluetooth", ATTRS{idVendor}=="foo", ATTRS={idProduct}="bar", RUN+="some_no_op_script.sh"

Offline

#2 2015-03-19 00:14:10

Knute
Member
From: Minot, ND
Registered: 2009-03-17
Posts: 604

Re: Persistent mapping from BT hardware to hci name

hciconfig has the name option where you can both get and set the name.


Knute

Offline

#3 2015-03-19 00:48:17

yoooyle
Member
Registered: 2015-02-25
Posts: 2

Re: Persistent mapping from BT hardware to hci name

I tried that. The name is only recognized by hciconfig. not bdaddr, hcitool or other commands. For example, i can't do

hcitool -i theNewName scan

I have to do

hcitool -i hci1 scan

Offline

Board footer

Powered by FluxBB