April 2021 - coreboot - mail.coreboot.org

Resource allocator v3
by Kyösti Mälkki April 29, 2021

April 29, 2021

Hi According to Documentation/releases/coreboot-4.14-relnotes.md we are expecting following chipset deprecations due to RESOURCE_ALLOCATOR_V3: * northbridge/amd/pi/00630F01 * northbridge/amd/pi/00730F01 * northbridge/amd/pi/00660F01 (already removed) * northbridge/amd/agesa/family14 * northbridge/amd/agesa/family15tn * northbridge/amd/agesa/family16kb Any progress or any interest to get these fixed? Regards, Kyösti

3 3

Building Coreboot with Nix
by Julian Stecklina April 29, 2021

April 29, 2021

Hi, I'm trying to build Coreboot with Nix [1] and am facing some issues. I'm wondering whether someone has already tried this before and can give some pointers. My specific problem is how to nicely package the toolchain that coreboot requires. Any hints are appreciated. :) I did discover https://nixos.wiki/wiki/Coreboot, but this doesn't help with the toolchain issue when coreboot is built as a Nix derivation... Thanks! Julian [1] https://nixos.org/

5 5

[coreboot - Cleanup #308] (New) Deal with walkcbfs_asm
by coreboot＠fe80.eu April 28, 2021

April 28, 2021

Issue #308 has been reported by Patrick Georgi. ---------------------------------------- Cleanup #308: Deal with walkcbfs_asm https://ticket.coreboot.org/issues/308 * Author: Patrick Georgi * Status: New * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- To remove the CBFS master header, walkcbfs_asm needs to either be made aware of fmap or removed. Current users (as determined by Arthur): - Updating microcode before CAR on systems that don't do µcode updates through FIT - Finding FSP-T on builds that use it (which is a bad idea anyway for root of trust concerns) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

1 0

[coreboot - Feature #307] (New) Support FMAP in SeaBIOS
by coreboot＠fe80.eu April 28, 2021

April 28, 2021

Issue #307 has been reported by Patrick Georgi. ---------------------------------------- Feature #307: Support FMAP in SeaBIOS https://ticket.coreboot.org/issues/307 * Author: Patrick Georgi * Status: New * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- SeaBIOS requires the CBFS master header to find the start address of the CBFS structure. It should parse the FMAP instead. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

1 0

[coreboot - Cleanup #306] (New) Get rid of CBFS master header
by coreboot＠fe80.eu April 28, 2021

April 28, 2021

Issue #306 has been reported by Patrick Georgi. ---------------------------------------- Cleanup #306: Get rid of CBFS master header https://ticket.coreboot.org/issues/306 * Author: Patrick Georgi * Status: New * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- The CBFS master header has been used for some basic partitioning of the flash before we established the use of FMAP. Now that FMAP is the default mechanism across the tree, we should get rid of the master header. This is a tracking issue to collect what needs to be done before we can retire the master header for good. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

1 0

Intent to release coreboot 4.14 on May 10
by Patrick Georgi April 26, 2021

April 26, 2021

Hi everybody, This email starts the release process for coreboot 4.14, so we're now at the "~2 weeks prior to release" step in our https://doc.coreboot.org/releases/checklist.html As usual, our releases don't denote any particular feature or stability milestone, they only serve two purposes: 1. Avoid the impression that coreboot is dead - an idea that actually came up before we started doing time-based releases 2. Provide anchor points that downstream coreboot users can use to base their work against if they wish to do so What everybody can do: Consider testing the devices you have against our current master branch, send in board-status reports so boards are known-good in https://coreboot.org/status/board-status.html, report or, even better, fix issues you encounter. As a developer, please consider if your large scale tree change can wait for after the release so that the tree can settle down a bit. But also, if you have large changes that are waiting (such as toolchain updates), you could already start to bring them in shape to merge after the release! Also, please check out the release notes in Documentation/releases/ coreboot-4.14-relnotes.md to see if any notable work of the last 6 months is missing there. Addition and deletion of mainboards and SoCs will be added shortly before the release with script assistance, but everything else won't be. Patches to extend our release notes are appreciated! Thanks y'all for making coreboot what it is now. As a release manager I'll merely put another label on it :-) Best regards, Patrick -- Google Germany GmbH, ABC-Str. 19, 20354 Hamburg Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg Geschäftsführer: Paul Manicle, Halimah DeLaine Prado

2 1

T480 support
by Даниил Солодов April 23, 2021

April 23, 2021

Is it planning support Thinkpad T480 model?

1 0

New Defects reported by Coverity Scan for coreboot
by scan-admin＠coverity.com April 23, 2021

April 23, 2021

Hi, Please find the latest report on new defect(s) introduced to coreboot found with Coverity Scan. 1 new defect(s) introduced to coreboot found with Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 1 of 1 defect(s) ** CID 1452697: Resource leaks (RESOURCE_LEAK) /tests/lib/region_file-test.c: 32 in setup_region_file_test_group() ________________________________________________________________________________________________________ *** CID 1452697: Resource leaks (RESOURCE_LEAK) /tests/lib/region_file-test.c: 32 in setup_region_file_test_group() 26 27 rdev_chain_mem_rw(dev, mem_buffer, REGION_FILE_BUFFER_SIZE); 28 *state = dev; 29 30 clear_region_file(dev); 31 >>> CID 1452697: Resource leaks (RESOURCE_LEAK) >>> Variable "mem_buffer" going out of scope leaks the storage it points to. 32 return 0; 33 } 34 35 static int teardown_region_file_test_group(void **state) 36 { 37 struct region_device *dev = *state; ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u15810271.ct.sendgrid.net/ls/click?upn=HRESupC-2F2Czv4BOaCWWCy7my0P…

1 0

[coreboot - Bug #305] (New) Thermal sensors on Thinkpad X201 no longer working
by coreboot＠fe80.eu April 23, 2021

April 23, 2021

Issue #305 has been reported by Stefan Ott. ---------------------------------------- Bug #305: Thermal sensors on Thinkpad X201 no longer working https://ticket.coreboot.org/issues/305 * Author: Stefan Ott * Status: New * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- The thermal sensors on my Thinkpad are no longer working with the latest version of coreboot. Normally, the values should look like this: # cat /proc/acpi/ibm/thermal temperatures: 68 0 0 0 0 0 0 0 # sensors thinkpad-isa-0000 thinkpad-isa-0000 Adapter: ISA adapter fan1: 3440 RPM temp1: +68.0°C Now they look like this instead: # cat /proc/acpi/ibm/thermal temperatures: -128 0 0 0 0 0 0 0 # sensors thinkpad-isa-0000 thinkpad-isa-0000 Adapter: ISA adapter fan1: 0 RPM temp1: N/A It seems that this patch broke things: https://review.coreboot.org/c/coreboot/+/51072 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

1 0

Help compiling image for Thinkpad T60
by cuckoohead＠disroot.org April 20, 2021

April 20, 2021

I'm following the instructions of the Build HOWTO section of the Coreboot Wiki (https://www.coreboot.org/Build_HOWTO) and I'm having some issues. Following the quote from the wiki "It is worth checking the Supported Motherboards (https://coreboot.org/status/board-status.html) page to see if your mainboard is known to work with a particular version of coreboot. If your board is listed and you want to try a known-working version, click the "upstream tree" link to find the commit hash and then check it out in git:" So I find the commit hash and run: git checkout 87e36c442e33388493f259bfa14db460a4f02753 Which returns the output: warning: unable to rmdir '3rdparty/intel-sec-tools': Directory not empty warning: unable to rmdir '3rdparty/qc_blobs': Directory not empty warning: unable to rmdir '3rdparty/stm': Directory not empty Updating files: 100% (8604/8604), done. M 3rdparty/amd_blobs M 3rdparty/arm-trusted-firmware M 3rdparty/blobs M 3rdparty/chromeec M 3rdparty/fsp M 3rdparty/intel-microcode M 3rdparty/libgfxinit M 3rdparty/libhwbase M 3rdparty/vboot Note: switching to '87e36c442e33388493f259bfa14db460a4f02753'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example: git switch -c <new-branch-name> Or undo this operation with: git switch - Turn off this advice by setting config variable advice.detachedHead to false If I try to proceed with: git submodule update --checkout I receive the output: fatal: remote error: upload-pack: not our ref 0ac1af437d2cc461b94bd2cdaa195e86dd481d37 Fetched in submodule path '3rdparty/amd_blobs', but it did not contain 0ac1af437d2cc461b94bd2cdaa195e86dd481d37. Direct fetching of that commit failed. I'm not that familiar with git so I apologize if this is a simple problem. Sorry for the spam too, I missclicked the return key.

1 0