-
-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
t440p/w541 marked UNTESTED (boot in 50s) : CONFIG_CBFS_SIZE of 8mb (changed to CONFIG_CBFS_SIZE=0xBE4FFF by need) #1825
Comments
Pinned issue |
Additionally, I've just tested on the W541 board from UNTESTED_w541-maximized (The path under UNTESTED_w541-hotp-maximized.config is inconsistent due to renaming to UNTESTED). As expected, boot time is over 50 seconds. |
@ResendeGHF Maybe its time to switch to native ram init #1711 ? (With its documented downsides) |
@ResendeGHF op updated. |
Also note that participating in upstream issue would make this go forward https://ticket.coreboot.org/issues/457 |
Proposed collaboration in s3 resume from suspend patchset at https://review.coreboot.org/c/coreboot/+/81897/comments/d4d3ed3a_d6c46137 If you see replies faster than I do, please ping me here. |
Why master was not enforcingUnfortunately reason was that anything CBFS bigger then 8mb will make Haswell boot in 50s, thanks to improper MRC blob we depend on.CONFIG_CBFS_SIZE=0xBE4FFF
as all other 12mb opaque flash chips from ivy bridge? (was 8mb). Merged as emergency fix: untested.Solution would be to switch to NRI #1711, which is not merged upstream.
Board owners: time to participate testing/reviewing/commenting upstream your need/appreciation of memory initialization being free under #1711.
OLD
#1826 was merged moving those boars to untested to prevent users from potential bricking without external programmers.
Testing needed from boards testers (BOARDS_TESTERS.md):
TESTED: Master roms will boot, but after 50s see #1825 (comment)
Therefore, t440p/w541 boards now build UNTESTED tagged board roms. Be warned.
The text was updated successfully, but these errors were encountered: