Upstream: U-Boot DRAM sizing for sun9i #28
Labels
No labels
blocked-physical
cleanup
hardware
infra
kernel
P1-critical
P2-high
P3-normal
P4-later
reliability
security
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tiagoagueda/a80#28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
U-Boot reports 2 GiB on a board with 4 GiB fitted; three separate bugs were involved and the
board now correctly sees 3.5 GiB. See 22-dram-4gb.md.
Independent of every kernel series here — different project, different list — so it can go
whenever it is ready.
patmanrather thanb4⚠️ Nothing has been submitted. See 42-upstreaming.md for routing,
order, mechanics, and the DCO / AI-assistance caveats. Patches are exported to
patches/,which is not the same as proposing them.
Unblocked 2026-08-29. #38 was the blocker on this and is now done: a full-range
mtestover 3503 MiB passed with 0 errors, and
bdinfostates the geometry independently as one0xe0000000bank.So the series can now say what was actually verified rather than implying it. Suggested
wording for the commit message, since "Linux boots and reports the right size" was the weak
part:
One caveat worth carrying: the top 81 MiB cannot be tested from U-Boot because U-Boot lives
there. It is a small fraction and the address-line walk covers the full span either way, but
it should be stated rather than glossed.