While it's nice to have basic support in the kernel, for people using
these devices for sequences / controlling a chain of neopixels / etc
they're going to need a custom kernel with the driver disabled in order
to access it from userland.

For release users this either locks them out of using syspatch
completely (if they do this by building -stable with custom config -
syspatch won't run at all with -stable), or at least from using syspatch
for kernel fixes (if using config -ef) - so it would be really nice to
have a better way around this before adding more drivers taking over
from existing device support.

Reply via email to