Can BlueZ D-BUS API identify local Bluetooth hardware version?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Can BlueZ D-BUS API identify local Bluetooth hardware version?
From: John Klug <John.Klug@xxxxxxxxxxxxx>
Date: Mon, 22 Aug 2022 16:12:37 +0000
Accept-language: en-US
Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=multitech.com;
Msip_labels:

I did a diff of "bluetoothctl show [addr]" between Bluetooth 4.0 and 5.1.

Address was random for 5.1 (will that always be the case)?

SupportedIncludes: tx-power was additional for 5.1.

What other API's could be used in a program to discern this?





John Klug

Follow-Ups:
- Re: Can BlueZ D-BUS API identify local Bluetooth hardware version?
  - From: Luiz Augusto von Dentz

Prev by Date: RE: [BlueZ] test/test-mesh: Fix python warning
Next by Date: Re: Can BlueZ D-BUS API identify local Bluetooth hardware version?
Previous by thread: [linux-next:pending-fixes] BUILD SUCCESS 72d0e40cc07e06e5b11ddcf74ba68f7e04eacb16
Next by thread: Re: Can BlueZ D-BUS API identify local Bluetooth hardware version?
Index(es):
- Date
- Thread

[Index of Archives] [Bluez Devel] [Linux Wireless Networking] [Linux Wireless Personal Area Networking] [Linux ATH6KL] [Linux USB Devel] [Linux Media Drivers] [Linux Audio Users] [Linux Kernel] [Linux SCSI] [Big List of Linux Books]

Powered by Linux