Use upstream LED description on Unmatched
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Emil Renner Berthing | ||
Kinetic |
Fix Released
|
Undecided
|
Emil Renner Berthing | ||
linux-riscv (Ubuntu) |
Fix Released
|
Undecided
|
Emil Renner Berthing | ||
Kinetic |
Fix Released
|
Undecided
|
Emil Renner Berthing |
Bug Description
[Impact]
* The Ubuntu RISC-V kernel carries out-of-tree patches to enable
the two LEDs on the SiFive Unmatched board.
* There is now an upstream solution to enable the LEDs that appears
a little different from userspace. With the out-of-tree patches the
three colours in the RGB LED appears as 3 different LEDs, but upstream
models them as 1 RGB LED.
* Replacing the out-of-tree patches with the upstream solution will
make Ubuntu kernels behave like the upstream kernel going forward.
[Test Plan]
* Boot Ubuntu on the Unmatched board and look at how the LEDs show up
in /sys/class/leds
* Check that both the green D12 and all three colours of D2 can still
be controlled from userspace.
[Where problems could occur]
* Users may have scripts setting up LEDs that will no longer work when
updating to Kinetic with this change.
CVE References
description: | updated |
Changed in linux-riscv (Ubuntu): | |
assignee: | nobody → Emil Renner Berthing (esmil) |
Changed in linux (Ubuntu): | |
assignee: | nobody → Emil Renner Berthing (esmil) |
status: | Incomplete → New |
Changed in linux (Ubuntu): | |
status: | New → Incomplete |
Changed in linux-riscv (Ubuntu): | |
status: | New → In Progress |
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Committed |
Changed in linux (Ubuntu Kinetic): | |
status: | Fix Committed → Invalid |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1987513
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.