From: Johan Hedberg <johan.hedberg@gmail.com>
To: Randy Yates <yates@digitalsignallabs.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: BT_ADDR not updated
Date: Mon, 18 Feb 2013 10:55:51 +0200 [thread overview]
Message-ID: <20130218085551.GA11034@x220> (raw)
In-Reply-To: <87bobkjoqs.fsf@randy.site>
Hi Randy,
On Sat, Feb 16, 2013, Randy Yates wrote:
> This question is regarding bluez 5.2:
>
> i'm changing bt addr "on-the-fly" via a vendor-specific hcitool
> command but the bluetoothctl is not seeing the new address, even
> after a hciconfig hci0 reset
>
> however i do see the new address via "hcitool dev", so it's getting
> changed in the device
>
> is there some bug in bluez updating the device address on a reset?
The address is assumed to stay unchanged from the moment that the
existence of the controller is presented to user space, i.e. there is no
event through which user space would be notified of changes to its
address. If your hardware requires this kind of initialization (e.g. if
it doesn't have a proper address from the start) the best place for
writing the address would probably be the HCI driver's initialization
routine.
Johan
prev parent reply other threads:[~2013-02-18 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 14:51 BT_ADDR not updated Randy Yates
2013-02-18 8:55 ` Johan Hedberg [this message]
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=20130218085551.GA11034@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=yates@digitalsignallabs.com \
/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