coreboot-kgpe-d16/util/amdtools
Stefan Reinauer 14e2277962 Since some people disapprove of white space cleanups mixed in regular commits
while others dislike them being extra commits, let's clean them up once and
for all for the existing code. If it's ugly, let it only be ugly once :-)

Signed-off-by: Stefan Reinauer <stepan@coresystems.de>
Acked-by: Stefan Reinauer <stepan@coresystems.de>



git-svn-id: svn://svn.coreboot.org/coreboot/trunk@5507 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
2010-04-27 06:56:47 +00:00
..
example_input Add an initial version of some tools to compare (extended) K8 memory settings. 2009-10-28 19:41:52 +00:00
README Since some people disapprove of white space cleanups mixed in regular commits 2010-04-27 06:56:47 +00:00
k8-compare-pci-space.pl Since some people disapprove of white space cleanups mixed in regular commits 2010-04-27 06:56:47 +00:00
k8-interpret-extended-memory-settings.pl Since some people disapprove of white space cleanups mixed in regular commits 2010-04-27 06:56:47 +00:00
k8-read-mem-settings.sh Add an initial version of some tools to compare (extended) K8 memory settings. 2009-10-28 19:41:52 +00:00
parse-bkdg.pl Since some people disapprove of white space cleanups mixed in regular commits 2010-04-27 06:56:47 +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