4 ms·
Those proprietary implementations should not exist. Bluetooth is open protocol and there's no reason to not use open source implementations.
by vbezhenar 2y ago
Those proprietary implementations should not exist. Bluetooth is open protocol and there's no reason to not use open source implementations.
- rollcat 2y agoFrom TFA: > The ESP32 series of chips support open-source NimBLE and Bluedroid as Bluetooth host stacks. The undocumented commands in question (which implement the debug interface) are about to become documented, and Espressif was both transparent in their publication, and pledged for more transparency moving forward. How much more do you want?
- akimbostrawman 2y ago>How much more do you want? Be open (source) by default to prevent such issues from the start. A pledge does nothing, open code does.
- vbezhenar 2y agoI think that they handled this particular issue well. It was more rant about general state of things in the industry. I worked with Nordic chips and they also supply enormous 120 KB proprietary blob called SoftDevice which you supposed to put into your firmware and let it own all the interrupts. This is terrible experience.
- rollcat 2y agoI understand your objections, but I don't think I have to explain that anything directly touching wireless is already walking the edge of the regulatory abyss. But yeah, some vendors make it easier, others seem to just want developers to suffer.
- ChrisRR 2y agoJust because there are open source stacks, doesn't mean the radios implemented in silicon are open source