top | item 21859858

Show HN: Linux driver for the Xbox One wireless dongle

158 points| Medusalix | 6 years ago |github.com | reply

22 comments

order
[+] samueloph|6 years ago|reply
Thanks for working on it, I'll see if I can get it packaged to Debian during the holidays.
[+] Medusalix|6 years ago|reply
Having a package for Debian (and later on Ubuntu) would be really awesome. It's already available for Arch Linux and I expect the list of packages to be growing over the next few weeks.
[+] seba_dos1|6 years ago|reply
Finally! :) I have one with borked USB port (I think the 1537 one), if it works this may make it useful again.

Thanks for working on this!

[+] carc1n0gen|6 years ago|reply
Curious how you charge if if the usb is "borked"
[+] martinmunk|6 years ago|reply
Nice project! Initial thought: apart from ease of development, is there any reason to do it in user space? I looked into uinput before to get a Bluetooth mfi controller working, but couldn't figure out which modules of the kernel did what.
[+] Const-me|6 years ago|reply
Ease of development is underestimation.

I’ve built a few user space Linux drivers for SPI and USB devices. Was easy, I have consumed stable APIs exposed by usbdevfs, libudev, and a few others. No need to recompile OS kernel. Because Linux kernel API is stable, not only OS kernel upgrades don’t break my stuff, they don’t even require me to recompile my code.

Creating a kernel mode Linux driver is much harder in comparison.

Merging a driver into the mainline Linux is borderline impossible. Even Google with all their corporate resources and platinum membership of Linux foundation was unable to do so, instead they are supporting many thousands lines of patches: https://source.android.com/devices/architecture/kernel/andro...

It’s safe to assume you won’t be able to push your custom driver either. You’ll have to do it the same way as everyone else — patch locally. This is not trivial either, but this time the challenge is technical, not political, as Linux kernel doesn’t have stable API nor ABI: https://github.com/torvalds/linux/blob/master/Documentation/...

[+] loeg|6 years ago|reply
Until performance is an obstacle, writing drivers in user space first is all benefit. Quick prototyping, crashes don't bring down the system, choice of programming language, etc, etc.
[+] fulafel|6 years ago|reply
It's this is the major factor limiting driver development on Linux, so it hardly needs another reason. But security is another thing that userspace implementation can do better on, no idea about this case specifically.
[+] Medusalix|6 years ago|reply
One of the major points for me was how cumbersome the installation process for kernel modules is. Now I can just do make install which works on most Linux distributions.
[+] IlegCowcat|6 years ago|reply
> Most of the reverse engineering was done by capturing the communication between the dongle and a Windows PC using Wireshark

Haha that's pretty cool

[+] hnarn|6 years ago|reply
If Windows is the only platform (apart from the Xbox) where the dongle works, there's also not much of an option if you want to intercept valid traffic relatively easily.
[+] alufers|6 years ago|reply
Thank you so much! I was just to buy the Bluetooth ones but it seems like I don't have to.