a95cd265bd
The update_efs_spi_speed allows changing the SPI speed manually in a binary that has already been built. This will allow binaries not built for the EM100 SPI ROM emulator to be updated so that they will work. There is a corresponding change that will check to see if the EFS value has been modified from the original speed and will prevent coreboot from updating the SPI speed and mode. BUG=b:177233017 TEST=Update SPI speed in existing binary. See that SPI speed has changed. Signed-off-by: Martin Roth <martin@coreboot.org> Change-Id: I905a9fd8bd93a28aab927dffecbbcf24934b9e03 Reviewed-on: https://review.coreboot.org/c/coreboot/+/56644 Reviewed-by: Raul Rangel <rrangel@chromium.org> Reviewed-by: Karthik Ramasubramanian <kramasub@google.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org> |
||
---|---|---|
.. | ||
example_input | ||
README | ||
description.md | ||
k8-compare-pci-space.pl | ||
k8-interpret-extended-memory-settings.pl | ||
k8-read-mem-settings.sh | ||
parse-bkdg.pl | ||
update_efs_spi_speed |
README
This is a set of tools to compare (extended) K8 memory settings. Before you can use them, you need to massage the relevant BKDG sections into useable data. Here's how. First, you need to acquire a copy of the K8 BKDG. Go here: Rev F: http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/32559.pdf Then make sure pdftotext is installed (it's in the poppler-utils package on Debian/Ubuntu). Now run the bkdg through pdftotext: pdftotext -layout 32559.pdf 32559.txt Now extract sections 4.5.15 - 4.5.19 from the file, and save it separately, say as bkdg-raw.data. Finally run the txt file through the parse-bkdg.pl script like so: parse-bkdg.pl < bkdg-raw.data > bkdg.data Now we have the bkdg.data file that is used by the other scripts. If you want to test the scripts without doing all this work, you can use some sample input files from the 'example_input/' directory. -- Ward Vandewege, 2009-10-28. ward@jhvc.com