From: Sebastien Cayetanot <sebastien.cayetanot@linux.intel.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: BD address changed but pairing failed
Date: Mon, 06 Sep 2010 12:17:22 +0200 [thread overview]
Message-ID: <4C84BFB2.3000802@linux.intel.com> (raw)
In-Reply-To: <AANLkTi=9HR+iTm=baVdefQcd-Nb8Gchx3LN6q-CycMcq@mail.gmail.com>
Le 9/4/2010 9:07 PM, Luiz Augusto von Dentz a écrit :
> Hi,
>
> On Fri, Sep 3, 2010 at 1:30 PM, Sebastien Cayetanot
> <sebastien.cayetanot@linux.intel.com> wrote:
>> All,
>>
>> I'm currently facing an issue regarding the pairing of BT devices after
>> having change the BD_Addr.
>>
>>
>> I use a TI chip and also use hci command or bdaddr script to modify the
>> bd_addr
>>
>> I'm also using the bluez-4.69
>>
>> I change the BD_Addr using the bdaddr scripts provided into the bluez src.
>>
>> When other devices scan me, the new address is seen but hciconfig still show
>> the old BD address.
>>
>> I have sent the hcitool cmd to read the bd_addr and after the hciconfig
>> return the one.
>>
>> I'm discoverable with the new BD address.
>>
>> But When I try to pair an A2DP headset or BT Keyboard/Mouse it failed since
>> BD_Addr change.
>>
>> I have try to use directly the hcitool cmd using the vendor specific command
>> but I got the same result.
>>
>> I have tried to kill bluetooth daemon and restart it after having change the
>> bd_addr. Still failing.
>>
>> I have tried to kill bluetooth daemon before changing the BD adress and
>> start it after the change it still fail.
>>
>> I have also tried to power on/off interface. still the issue
>>
>> I think that something is "broken" is bluez when the BD_Addr is changed.
>>
>> Is someone already seen this issue ?
> I don't think you are suppose to change the address like that, it is
> supposed to be done once in the chip initialization and then keep it
> like that forever, so I guess there is something wrong if the chip is
> already initialize with the wrong address. What are you trying achieve
> with this?
>
Surely not but regarding some tests scripts I have seen on bluez, I
suppose that's possible. Perhaps, some chips support and other don't.
I have tried to change the BD_Address during the BT initialization and
prior any HCI command sent to the chip and it works.
I expected the same behavior than observed on WLAN : I have changed the
WLAN MAC address after and everything works fine.
Regards.
Sebastien
next prev parent reply other threads:[~2010-09-06 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 10:30 BD address changed but pairing failed Sebastien Cayetanot
2010-09-04 19:07 ` Luiz Augusto von Dentz
2010-09-06 10:17 ` Sebastien Cayetanot [this message]
2010-09-07 19:58 ` Marcel Holtmann
2010-09-07 22:25 ` Sebastien Cayetanot
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=4C84BFB2.3000802@linux.intel.com \
--to=sebastien.cayetanot@linux.intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).