f57bf3f994
This change is mostly from CB:56644 patchset 3. Signed-off-by: Martin Roth <martin@coreboot.org> Signed-off-by: Felix Held <felix-coreboot@felixheld.de> Change-Id: I4cb9bbb3d7fd5d7c9e33fbf656301c0beb2f1b47 Reviewed-on: https://review.coreboot.org/c/coreboot/+/61894 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Paul Menzel <paulepanter@mailbox.org> Reviewed-by: Raul Rangel <rrangel@chromium.org> |
||
|---|---|---|
| .. | ||
| example_input | ||
| README.md | ||
| 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.md
amdtools
Various tools for AMD platforms
A set of tools to compare (extended) K8 memory settings.
- k8-compare-pci-space.pl
- k8-interpret-extended-memory-settings.pl
- k8-read-mem-settings.sh
- parse-bkdg.pl
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
- Make sure pdftotext is installed (it's in the poppler-utils package on Debian/Ubuntu).
- Run the bkdg through pdftotext:
pdftotext -layout 32559.pdf 32559.txt - 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.