[Bug 1965260] [NEW] SRU: Detect RAM size automatically

Launchpad Bug Tracker 1965260 at bugs.launchpad.net
Tue Jun 21 13:07:00 UTC 2022


You have been subscribed to a public bug by Alexandre Ghiti (alexghiti):

https://github.com/smaeul/sun20i_d1_spl/commits/d1-2022-01-22, commit
525883d3721f4c4d78b498e780b44e85d0676abf contains patches to detect the
RAM size automatically.

[Impact]

If the memory is not discovered automatically, the Nezha can't boot
without an additional memory node in the device tree: the issue is that
the Nezha boards comes now with 2 different amounts of memory, 1GB or
2GB. So the additional device tree node can't cover both boards.

It is essential to backport this fix to Jammy as we intend to provide
first support for the Nezha board in 22.04.1.

[Test Plan]

To test the fix is correct, one can simply use this nezha-boot0 and
check that the next stage bootloader (u-boot-nezha) advertises the right
amount of memory for the board, which is displayed at boot right after
the banner:

U-Boot 2022.04 (Apr 21 2022 - 09:19:39 +0000)

DRAM:  1 GiB
sunxi_set_gate: (CLK#24) unhandled

Additionally to that, do general dogfooding to see if the new version
still works as expected.

[Where problems could occur]

The update will not introduce regressions as this package is *not* used
since we did not deliver images for the Nezha board yet, support for
this board is an additional feature scheduled for 22.04.1.

[Other Info]

Note that this only fixes the memory detection from boot0 to u-boot,
another similar patch is needed for u-boot-nezha to patch the kernel
device tree.

Note #2: the SRU backports more than just the fix, see comment #10.

** Affects: nezha-boot0 (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: nezha-boot0 (Ubuntu Jammy)
     Importance: Undecided
         Status: Fix Committed


** Tags: fr-1944 verification-needed verification-needed-jammy
-- 
SRU: Detect RAM size automatically
https://bugs.launchpad.net/bugs/1965260
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list