hci_dev_get...rom_property(9)
π¦ hci_dev_get_bd_addr_from_property π¦
okay bestie, welcome to the Kernel API Manual β¨ this one's a lil' function page from the Bluetooth corner of the kernel, and honestly? it's giving "quiet hero energy" π
πΈ NAME πΈ
hci_dev_get_bd_addr_from_property β literally the glow-up moment where we go grab the Bluetooth Device Address (BD_ADDR) for a HCI device, and we get it from a firmware node property π
β¨ SYNOPSIS β¨
void hci_dev_get_bd_addr_from_property (struct hci_dev *hdev );
that's it. that's the whole vibe. no return value, she just does it π«Ά
π ARGUMENTS π
hdevβ the HCI device π like, the one main character we're doing all this for
π DESCRIPTION π
so what she does is: search the firmware node for local-bd-address πβ¨ that's the mission, that's the whole quest.
and here's the important part, ngl β all-zero BD addresses get rejected π and that's on purpose, because a zero address could totally be one of those properties that exist in the firmware tables but the firmware never actually updated. like, imagine the DTS defines local-bd-address with a zero BD address in it? yeah. that's a whole fake-out π so we don't fall for it. periodt.
fr fr, don't skip this check β a zero BD_ADDR is not a real address, it's a "nobody filled this in yet" situation π
π SEE ALSO π
- Kernel file
./net/bluetooth/hci_sync.cβ go read it, iykyk π§
and that's the page, bestie π it's from the ./net/bluetooth corner of the tree, dated October 2026 β slay, iconic, no notes π
π
β mwah β
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms