Support LicheeRV and PolarFire RISC-V platforms in jammy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
livecd-rootfs (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
As part of our HWE story, we want to support two new platforms (available in kinetic/lunar): the LicheeRV and the PolarFire Icicle Kit. To do this, we need to backport some of the livecd-rootfs changes for building those images.
https:/
* Add support for the LicheeRV board (SUBARCH=licheerv)
* Add support for the PolarFire Icicle Kit board (SUBARCH=icicle)
* Reduce initrd size for Nezha and LicheeRV boards
* Use efi=debug earlycon on kernel command line
[Test Case]
Build official PROPOSED=1 images for jammy for licheerv and icicle SUBARCHes.
Additionally to this, make sure existing RISC-V preinstalled images still build correctly. Reach out to the CPC to check if cloud images for RISC-V still build correctly with the new livecd-rootfs.
[Regression Potential]
The only regression potential is breaking other RISC-V related images, but this should be mitigated by the additional testing steps provided in the Test Case.
tags: |
added: verification-done-jammy removed: verification-needed-jammy |
Changed in livecd-rootfs (Ubuntu): | |
status: | New → Invalid |
Changed in livecd-rootfs (Ubuntu Jammy): | |
milestone: | none → ubuntu-22.04.2 |
Changed in livecd-rootfs (Ubuntu): | |
milestone: | ubuntu-22.04.2 → none |
Hello Łukasz, or anyone else affected,
Accepted livecd-rootfs into jammy-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ livecd- rootfs/ 2.765.13 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification- needed- jammy to verification- done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- jammy. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.