All of lore.kernel.org
 help / color / mirror / Atom feed
* hciattach alternative to change default address after upgrading to BlueZ 5.47
@ 2018-02-12 11:22 sudeepta bhuyan
  2018-02-12 14:08 ` Marcel Holtmann
  0 siblings, 1 reply; 3+ messages in thread
From: sudeepta bhuyan @ 2018-02-12 11:22 UTC (permalink / raw)
  To: linux-bluetooth

Hello all,

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?

Thanks,
Sudeepta

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: hciattach alternative to change default address after upgrading to BlueZ 5.47
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Marcel Holtmann @ 2018-02-12 14:08 UTC (permalink / raw)
  To: sudeepta bhuyan; +Cc: linux-bluetooth

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


^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: hciattach alternative to change default address after upgrading to BlueZ 5.47
  2018-02-12 14:08 ` Marcel Holtmann
@ 2018-02-14 10:02   ` sudeepta bhuyan
  0 siblings, 0 replies; 3+ messages in thread
From: sudeepta bhuyan @ 2018-02-14 10:02 UTC (permalink / raw)
  To: Marcel Holtmann; +Cc: linux-bluetooth

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
>

^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-02-14 10:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.