Emulation/switch-coreboot
1
0
Fork 0
mirror of https://github.com/fail0verflow/switch-coreboot.git synced 2025-05-04 01:39:18 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions
switch-coreboot/util/amdtools
History
Exact
Paul Menzel cbe21ed1e1 UPSTREAM: Use more secure HTTPS URLs for coreboot sites 
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'
```

BUG=none
BRANCH=none
TEST=none

Change-Id: I881e55138a6114c67585ce37d4d719fe2626b83a
Signed-off-by: Patrick Georgi <pgeorgi@google.com>
Original-Commit-Id: a8843dee58
Original-Change-Id: If53f8b66f1ac72fb1a38fa392b26eade9963c369
Original-Signed-off-by: Paul Menzel <paulepanter@users.sourceforge.net>
Original-Reviewed-on: https://review.coreboot.org/20034
Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Original-Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Reviewed-on: https://chromium-review.googlesource.com/528256
Commit-Ready: Patrick Georgi <pgeorgi@chromium.org>
Tested-by: Patrick Georgi <pgeorgi@chromium.org>
Reviewed-by: Patrick Georgi <pgeorgi@chromium.org>
2017-06-12 08:47:49 -07:00
..
example_input Remove empty lines at end of file 2015-06-08 00:55:07 +02:00
k8-compare-pci-space.pl UPSTREAM: Use more secure HTTPS URLs for coreboot sites 2017-06-12 08:47:49 -07:00
k8-interpret-extended-memory-settings.pl UPSTREAM: Use more secure HTTPS URLs for coreboot sites 2017-06-12 08:47:49 -07:00
k8-read-mem-settings.sh Remove empty lines at end of file 2015-06-08 00:55:07 +02:00
parse-bkdg.pl UPSTREAM: Use more secure HTTPS URLs for coreboot sites 2017-06-12 08:47:49 -07:00
README Remove empty lines at end of file 2015-06-08 00:55:07 +02: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