I find the whole bluetooth issues ominous.
For one the bes2600 driver's source headers show
/*
* ..
* Copyright © 2022, Bestechnic
* ..
*/
Which means they wrote the driver
They being the makers and suppliers of the bes2600 module.
All of the commands in the op table except for powering on and off wifi and bluetooth
are not implemented.
What's of note is that the power on / off commands that are implemented use the sdio interface
and not the uart interface which is what is used to communicate with the bluetooth transceiver (except for powering on/off which uses sdio).
This means the driver does not talk at all to the uart. The bluetooth transceiver.
Which is strange since the module has a bluetooth transceiver on the uart interface and the driver, as mentioned,
is developed by the module supplier.
It seems they left it out on purpose.
From my research Linux uses Bluez for all things bluetooth and Linux can support bluetooth controllers
out of the box without 3rd party drivers. If this is true the driver not having any substantial bluetooth
implementation save for powering on and off the transceivers makes sense.
However when trying bluetoothctl list, there is nothing output. This indicates that the bluetooth controller
is not supported by bluetoothctl and hence it seems bluez.
Of course I could be getting Bluez and it's capabilitites all wrong here and 3rd party drivers are needed for Bluez to do it's thing and the bes2600 driver written by Bestechnic is in fact incomplete, but that's just too far fetched.
Something is not being said about the bes2600 bluetooth driver, bluez, their place on the pinetab2 and what is entailed exaclty to get bluetooth working.
The makers of the pinetab2 need to speak up here and say what's going on beyond just a simple "the bluetooth driver needs to be implemented".
I am hard pressed to believe that Bestechnic didn't leave the driver incomplete by design and that the kernel takes care of what they left out. At least on most devices.
??
For one the bes2600 driver's source headers show
/*
* ..
* Copyright © 2022, Bestechnic
* ..
*/
Which means they wrote the driver
They being the makers and suppliers of the bes2600 module.
All of the commands in the op table except for powering on and off wifi and bluetooth
are not implemented.
What's of note is that the power on / off commands that are implemented use the sdio interface
and not the uart interface which is what is used to communicate with the bluetooth transceiver (except for powering on/off which uses sdio).
This means the driver does not talk at all to the uart. The bluetooth transceiver.
Which is strange since the module has a bluetooth transceiver on the uart interface and the driver, as mentioned,
is developed by the module supplier.
It seems they left it out on purpose.
From my research Linux uses Bluez for all things bluetooth and Linux can support bluetooth controllers
out of the box without 3rd party drivers. If this is true the driver not having any substantial bluetooth
implementation save for powering on and off the transceivers makes sense.
However when trying bluetoothctl list, there is nothing output. This indicates that the bluetooth controller
is not supported by bluetoothctl and hence it seems bluez.
Of course I could be getting Bluez and it's capabilitites all wrong here and 3rd party drivers are needed for Bluez to do it's thing and the bes2600 driver written by Bestechnic is in fact incomplete, but that's just too far fetched.
Something is not being said about the bes2600 bluetooth driver, bluez, their place on the pinetab2 and what is entailed exaclty to get bluetooth working.
The makers of the pinetab2 need to speak up here and say what's going on beyond just a simple "the bluetooth driver needs to be implemented".
I am hard pressed to believe that Bestechnic didn't leave the driver incomplete by design and that the kernel takes care of what they left out. At least on most devices.
??
