coreboot-kgpe-d16

History

Yegor Timoshenko c2e4941367 treewide: use /usr/bin/env where appropriate Some Unix systems (GuixSD, NixOS) do not install programs like Bash and Python to /usr/bin, and /usr/bin/env has to be used to locate these instead. Change-Id: I7546bcb881c532adc984577ecb0ee2ec4f2efe00 Signed-off-by: Yegor Timoshenko <yegortimoshenko@riseup.net> Reviewed-on: https://review.coreboot.org/28953 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Patrick Georgi <pgeorgi@google.com>		2018-11-17 07:32:03 +00:00
..
example_input	…
README	…
description.md	…
k8-compare-pci-space.pl	treewide: use /usr/bin/env where appropriate	2018-11-17 07:32:03 +00:00
k8-interpret-extended-memory-settings.pl	treewide: use /usr/bin/env where appropriate	2018-11-17 07:32:03 +00:00
k8-read-mem-settings.sh	treewide: use /usr/bin/env where appropriate	2018-11-17 07:32:03 +00:00
parse-bkdg.pl	treewide: use /usr/bin/env where appropriate	2018-11-17 07:32:03 +00:00

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