* Connecting to a BR/EDR+BLE device a via dbus?
@ 2022-11-17 16:09 Simon Vogl
2022-11-17 21:56 ` Luiz Augusto von Dentz
0 siblings, 1 reply; 2+ messages in thread
From: Simon Vogl @ 2022-11-17 16:09 UTC (permalink / raw
To: linux-bluetooth
Dear all,
we are communicating with a headset-ish device that offers classic
bluetooth services and BLE characteristics in parallel.
We have code to talk to the Bluetooth classic part via bluetoothd/dbus,
and we have code for talking to the BLE parts based on the C-library /
gatt-client code ; both run in parallel for some time but not
super-stable, so I'd like to move the code over to a dbus version.
As the device starts advertising BLE characteristics only after a
classic connection has been established, it appears as a Bluetooth
classic device on the system bus, and I did not find a way to start GATT
discovery via the 'official' dbus-API.
I don't fear to tweak bluetoothd nor ~ctl, but would like to know if
someone already some development going in that direction?
Simon
--
VoXel Interaction Design |www.voxel.at
DI Dr.techn. Simon Vogl |simon@voxel.at
Tomaschekweg 46 | +43 650 2323 555
A-4040 Linz - Austria |
Office address: Industriezeile 35, 4020 Linz (2nd floor)
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Connecting to a BR/EDR+BLE device a via dbus?
2022-11-17 16:09 Connecting to a BR/EDR+BLE device a via dbus? Simon Vogl
@ 2022-11-17 21:56 ` Luiz Augusto von Dentz
0 siblings, 0 replies; 2+ messages in thread
From: Luiz Augusto von Dentz @ 2022-11-17 21:56 UTC (permalink / raw
To: Simon Vogl; +Cc: linux-bluetooth
Hi Simon,
On Thu, Nov 17, 2022 at 8:20 AM Simon Vogl <simon@voxel.at> wrote:
>
> Dear all,
>
> we are communicating with a headset-ish device that offers classic
> bluetooth services and BLE characteristics in parallel.
>
> We have code to talk to the Bluetooth classic part via bluetoothd/dbus,
> and we have code for talking to the BLE parts based on the C-library /
> gatt-client code ; both run in parallel for some time but not
> super-stable, so I'd like to move the code over to a dbus version.
>
> As the device starts advertising BLE characteristics only after a
> classic connection has been established, it appears as a Bluetooth
> classic device on the system bus, and I did not find a way to start GATT
> discovery via the 'official' dbus-API.
>
> I don't fear to tweak bluetoothd nor ~ctl, but would like to know if
> someone already some development going in that direction?
Perhaps what is needed is to connect ATT over BREDR that way you don't
need 2 bearers to be connected, bt_att already supports connecting
over classic but we never took the step to connect ATT once we figured
it supported the ATT PSM given is not very common to have a classic
profile that uses GATT attributes.
> Simon
>
> --
>
> VoXel Interaction Design |www.voxel.at
> DI Dr.techn. Simon Vogl |simon@voxel.at
> Tomaschekweg 46 | +43 650 2323 555
> A-4040 Linz - Austria |
> Office address: Industriezeile 35, 4020 Linz (2nd floor)
>
--
Luiz Augusto von Dentz
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-11-17 21:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-11-17 16:09 Connecting to a BR/EDR+BLE device a via dbus? Simon Vogl
2022-11-17 21:56 ` Luiz Augusto von Dentz
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 read-only IMAP folder(s) and NNTP newsgroup(s).