a8843dee58
The coreboot sites support HTTPS, and requests over HTTP with SSL are also redirected. So use the more secure URLs, which also saves a request most of the times, as nothing needs to be redirected. Run the command below to replace all occurences. ``` $ git grep -l -E 'http://(www.|review.|)coreboot.org' | xargs sed -i 's,http://\(.*\)coreboot.org,https://\1coreboot.org,g' ``` Change-Id: If53f8b66f1ac72fb1a38fa392b26eade9963c369 Signed-off-by: Paul Menzel <paulepanter@users.sourceforge.net> Reviewed-on: https://review.coreboot.org/20034 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Patrick Georgi <pgeorgi@google.com> |
||
---|---|---|
.. | ||
example_input | ||
k8-compare-pci-space.pl | ||
k8-interpret-extended-memory-settings.pl | ||
k8-read-mem-settings.sh | ||
parse-bkdg.pl | ||
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