Re: Persistent mapping from BT hardware to hci name

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Yey,

> 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". It doesn't work with BT.
> 
> Here is the udev rule:
> SUBSYSTEM="bluetooth", ATTRS{idVendor}=="foo",
> ATTRS={idProduct}="bar", RUN+="some_no_op_script.sh"

renaming of Bluetooth HCI interfaces is not supported. Just give the name as parameter to the script you are executing. udev actually knows the name of the Bluetooth HCI interface.

Regards

Marcel

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux