this post was submitted on 04 Feb 2024
79 points (94.4% liked)

Linux

48287 readers
613 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
79
submitted 9 months ago* (last edited 9 months ago) by djtech@lemmy.world to c/linux@lemmy.ml
 

Hi everybody,

i'm a long time Debian user and, while i've always loved the Linux experience, the bluetooth side of things was always a little bit... painful.

Lately, i've been digging on how bluetooth on Linux works (i knew about BlueZ, but i didn't know about HCI sockets, standard protocols for bluetooth controllers, ...). Seeing how Android manages to work fine with bluetooth (yes, i know, money and company support, blah blah blah), i was thinking about re-writing the bluetooth daemon, in order to be modern, modular, safe (written in Rust), stable and retro-compatible (exposes the same D-Bus APIs as BlueZ) I already found some documents about HCI socket in Linux, HCI communication with bluetooth controllers, HID standards for Bluetooth, etc...

My questions are:

  • is this a good idea?
  • does somebody want to collaborate?

Thanks for reading.

EDIT: The repository is https://github.com/djtech-dev/reblued but at the moment is pretty much empty, just the project's skeleton, license, README and disussions for collaborators.

you are viewing a single comment's thread
view the rest of the comments
[–] djtech@lemmy.world 6 points 9 months ago (1 children)

Thanks for your reply; i won't work with firmware-level aspects of the stack, as my plan is to write the userspace daemon, while keeping the kernel-levels modules identical and to communicate to them via HCI sockets, as they are implemented by Linux and with them I can talk directly to the bluetooth controllers.

I'll check out Android's project and double-check for security vulnerabilities in older version of the protocols tho, so thank you again for replying.

[–] rcbrk@lemmy.ml 1 points 9 months ago

double-check for security vulnerabilities

triple-check is better.