linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: sudeepta bhuyan <sudeepta.bhuyan@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: hciattach alternative to change default address after upgrading to BlueZ 5.47
Date: Wed, 14 Feb 2018 15:32:31 +0530	[thread overview]
Message-ID: <CA+TC0NrLx9aMPtYTGrcROzOrmKL++f0RwMdc7jxYfwFs_669Mg@mail.gmail.com> (raw)
In-Reply-To: <B26A4952-B5DC-47BB-B45B-5D95FAEE6D98@holtmann.org>

Thanks Marcel. I was able to get it done using btmgmt.

Sudeepta

On Mon, Feb 12, 2018 at 7:38 PM, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Sudeepta,
>
>> Prior to upgrading BlueZ to 5.47 in my project, I was using hciattach
>> to set the UART device's address before starting bluetoothd.
>>
>> hciattach /dev/ttyS2 bcm43xx flow nosleep xx:xx:xx:xx:xx
>>
>> However since hciattach is deprecated in newer BlueZ, I am now using
>> btattach instead to do the same. But btattach does not provide an
>> option to set the bluetooth address of the device.
>>
>> What is the standard procedure to set the bluetooth address of the
>> UART device using newer BlueZ tools?
>
> there is btmgmt public-addr command that will work if your driver supports hdev->set_bdaddr. For Broadcom chips that should be fully supported.
>
> Regards
>
> Marcel
>

      reply	other threads:[~2018-02-14 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 11:22 hciattach alternative to change default address after upgrading to BlueZ 5.47 sudeepta bhuyan
2018-02-12 14:08 ` Marcel Holtmann
2018-02-14 10:02   ` sudeepta bhuyan [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=CA+TC0NrLx9aMPtYTGrcROzOrmKL++f0RwMdc7jxYfwFs_669Mg@mail.gmail.com \
    --to=sudeepta.bhuyan@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /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).