New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 900272 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

Expose FMAP offset in coreboot table

Project Member Reported by cjmcdonald@chromium.org, Oct 30

Issue description

"One of the big problems is that we don't know where the FMAP is. This requires reading the entire SPI flash and looking for a magic string. Coreboot knows where the FMAP is, so we are going to expose the fmap address via a coreboot table.

Additionally we will also update the coreboot kernel module to expose the new coreboot table via a sysfs entry. We can then update flashrom to look at this sysfs entry so we don't need to read the entire flash."

"coreboot/src/lib/coreboot_table.c:lb_boot_media_params: The fmap_offset is written into LB_TAG_BOOT_MEDIA_PARAMS
coreboot/util/cbmem/cbmem.c:parse_cbtable_entries: Can be update to parse the LB_TAG_BOOT_MEDIA_PARAMS tag. This way we can inspect the boot params using `cbmem`"

"See src/third_party/kernel/v4.14/drivers/firmware/google for the kernel module that exposes coreboot the tables. We can add a module to expose the fmap."
 

Sign in to add a comment