2 ms·
Bluetooth on Linux is an unprecedented abomination. You’d think most of it would be similar to network interfaces, handled by the kernel with commands such as
by Nextgrid 7y ago
Bluetooth on Linux is an unprecedented abomination.
You’d think most of it would be similar to network interfaces, handled by the kernel with commands such as ip, iptables, etc to configure it?
Wrong! Instead it’s mostly done in userspace and the tools to talk to it are using D-Bus which is an opaque, inconsistent, hard to understand mess which you can’t easily interact with programmatically.
As horrible as BT itself is I’d give the protocol itself a break in this case and focus on the terrible implementation.
- jmercouris 7y agoD-Bus is not part of the problem... it is just the common bus for communication between user processes. It is in fact a very straightforwards and well implemented specification.
- catalogia 7y agoThe debacle that was kdbus (and the technical motivation behind it in the first place) makes me wonder about that 'well implemented' part.
- bsder 7y ago> D-Bus is not part of the problem Only in the sense that the bluetooth maintainers never completed the port to D-Bus. So, 25% of what you need to do with bluetooth needs to be done via kernel anyway. Bluetooth on Linux is a prime example of how open source can fail.
- shakna 7y agoThe Bluetooth stack itself is an overcomplicated, terrible specification that leads to most Bluetooth chips have an _incomplete_ port of their own vital functionality. It isn't shocking that the thing to talk to them isn't complete.