Enable Nezha board

This bug is awaiting verification that the linux-nezha-5.17/5.17.0-1001.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

Verified that linux-nezha-5.17/5.17.0-1001.1 starts / attempts booting. More kernel config options will need tweaking to enable more things.

Dear Dimitri,

it is unclear to me why U-Boot should have any influence on the (non-)inclusion of a driver in the initramfs. Could you, please, add the missing information.

There is no guarantee that any update of U-Boot runs after the kernel change. A user can choose only to update the kernel. They could even run a custom U-Boot. Please avoid linking the kernel upgrade to any assumptions about U-Boot.

Best regards

Heinrich

Status changed to 'Confirmed' because the bug affects multiple users.

separately it was discussed that our nezha/licheerv do not have any sort of meta or config package installed (like we have on raspi, or concept-x13s images).

and that some may not use or have installed u-boot-nezha, because they have a custom u-boot. Meaning it is not safe to introduce a dependency on u-boot-nezha package which can wipe out ones custom u-boot config.

This bug was fixed in the package linux-riscv - 6.2.0-19.19.1+23.10.2

---------------
linux-riscv (6.2.0-19.19.1+23.10.2) mantic; urgency=medium

  * Miscellaneous Ubuntu changes
    - [Config] Update configs

linux-riscv (6.2.0-19.19.1+23.10.1) mantic; urgency=medium

  * mantic/linux-riscv: 6.2.0-19.19.1+23.10.1 -proposed tracker (LP: #2023551)

  * Packaging resync (LP: #1786013)
    - [Packaging] resync git-ubuntu-log
    - [Packaging] resync getabis
    - [Packaging] update helper scripts
    - [Packaging] update update.conf

  * Enable Nezha board (LP: #1975592)
    - clk: sunxi-ng: fix ccu_mmc_timing.c kernel-doc issues
    - clk: sunxi-ng: Avoid computing the rate twice
    - clk: sunxi-ng: Remove duplicate ARCH_SUNXI dependencies
    - clk: sunxi-ng: Move SoC driver conditions to dependencies
    - clk: sunxi-ng: d1: Allow building for R528/T113
    - clk: sunxi-ng: d1: Mark cpux clock as critical
    - dt-bindings: clock: Add D1 CAN bus gates and resets
    - clk: sunxi-ng: d1: Add CAN bus gates and resets
    - soc: sunxi: sram: Only iterate over SRAM children
    - dt-bindings: power: Add Allwinner D1 PPU
    - soc: sunxi: Add Allwinner D1 PPU driver
    - soc: sunxi: select CONFIG_PM
    - dt-bindings: crypto: sun8i-ce: Add compatible for D1
    - crypto: sun8i-ce - Add TRNG clock to the D1 variant
    - dmaengine: sun6i: Set the maximum segment size
    - dt-bindings: vendor-prefixes: Add Allwinner D1/D1s board vendors
    - dt-bindings: riscv: Add Allwinner D1/D1s board compatibles
    - riscv: dts: allwinner: Add the D1/D1s SoC devicetree
    - riscv: dts: allwinner: Add MangoPi MQ devicetree
    - riscv: dts: allwinner: Add Allwinner D1 Nezha devicetree
    - riscv: dts: allwinner: Add Sipeed Lichee RV devicetrees
    - riscv: dts: allwinner: Add MangoPi MQ Pro devicetree
    - riscv: dts: allwinner: Add Dongshan Nezha STU devicetree
    - riscv: Add the Allwinner SoC family Kconfig option
    - riscv: dts: allwinner: d1: Add power controller node
    - nvmem: sunxi_sid: Drop the workaround on A64
    - dt-bindings: timer: Add bindings for the RISC-V timer device
    - clocksource/drivers/timer-riscv: Set CLOCK_EVT_FEAT_C3STOP based on DT
    - clocksource/drivers/riscv: Increase the clock source rating
    - clocksource/drivers/riscv: Get rid of clocksource_arch_init() callback
    - dt-bindings: timer: sifive,clint: add comaptibles for T-Head's C9xx
    - riscv: dts: allwinner: d1: Add crypto engine node
    - riscv: dts: nezha-d1: add gpio-line-names
    - SAUCE: mmc: sunxi-mmc: Correct the maximum segment size
    - SAUCE: riscv: dts: allwinner: d1: Add misc nodes
    - SAUCE: riscv: dts: allwinner: Keep aldo regulator on
    - SAUCE: riscv: dts: allwinner: Add button on the Nezha board
    - SAUCE: riscv: dts: allwinner: Add button on the Lichee RV Dock
    - SAUCE: dt-bindings: nvmem: Allow bit offsets greater than a byte
    - SAUCE: nvmem: core: Support reading cells with >= 8 bit offsets
    - SAUCE: regulator: dt-bindings: Add Allwinner D1 LDOs
    - SAUCE: regulator: sun20i: Add support for Allwinner D1 LDOs
    - SAUCE: dt-bindings: sram: sunxi-sram: Add optional regulators child
    - SAUCE: dt-bindings: thermal...

This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

All autopkgtests for the newly accepted linux-meta-riscv (6.2.0.27.28.1) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

backport-iwlwifi-dkms/unknown (amd64)
cryptsetup/unknown (ppc64el, s390x)
ipmitool/unknown (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/lunar/update_excuses.html#linux-meta-riscv

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

This bug is awaiting verification that the linux-azure-6.5/6.5.0-1007.7~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-6.5' to 'verification-done-jammy-linux-azure-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.5' to 'verification-failed-jammy-linux-azure-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug is awaiting verification that the linux-aws-6.5/6.5.0-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-done-jammy-linux-aws-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-failed-jammy-linux-aws-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!