hci_dev_get...rom_property(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ 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