Today in discord #general I responded to a question about how to get one/both of these drivers into a ublue image. An ensuing chat prompted the creation of this issue for further discussion on the topic.
xpadneo specifically supports xbox one wireless controller via bluetooth
xone supports xbox one controllers/accessories via USB or the USB wireless dongle, aims to replace xpad
I've personally been building my own image atop ublue-os main and nvidia to add these two drivers. As akmods, like the nvidia drivers, they also need a signing key to support Secure Boot systems.
So this is a multipart question:
1) should both xpadneo
and xone
be added to ublue-os/main
? just one? which? why?
It was suggested in chat that we already have udev rules for various devices so adding drivers like this doesn't seem like much of a stretch.
xpadneo
pros:
- xbox one controllers will work via bluetooth (I don't believe they function via bluetooh without this driver)
xpadneo
cons:
xone
pros:
- xbox one wireless usb dongle support
- claims to be " a modern replacement for xpad, aiming to be compatible with Microsoft's Game Input Protocol (GIP)."
xone
cons:
- when installed will take priority over
xpad
for any supported devices, which some users may not prefer
2) If either are added, they need a signing key to enable Secure boot. How to handle this?
I'd personally suggest moving the existing key from nvidia
into main
and renaming it to ublue
such that main
would provide instructions to import like: sudo mokutil --import /etc/pki/akmods/certs/akmods-ublue.der
If so, it would be nice for this same key get re-used by the nvidia
build so that only one key needs to be imported.
Though, there could be two distinct keys.
For reference, here's my repo and build of these akmods: https://github.com/bsherman/ublue-kmods/