diff options
| author | Bill Richardson <wfrichar@chromium.org> | 2011-03-02 15:23:01 -0800 |
|---|---|---|
| committer | Bill Richardson <wfrichar@chromium.org> | 2011-03-02 15:23:01 -0800 |
| commit | 34092799b1cda3eddf6dfc8625c7699c5f5882ee (patch) | |
| tree | e1f1428a6c25947f6770619587ad9c2d07e8815e | |
| parent | 574684550064ab5ea4adcfd1b8d2c9ce92a0176b (diff) | |
| download | vboot-34092799b1cda3eddf6dfc8625c7699c5f5882ee.tar.gz | |
Fix mistakes in scripts/newbitmaps/README
Change-Id: I743060a27ab9d3caeeadde295883a18bdd864a1f
BUG=chrome-os-partner:2558
TEST=none
Documentation change only. No tests needed.
Review URL: http://codereview.chromium.org/6588127
| -rw-r--r-- | scripts/newbitmaps/README | 16 |
1 files changed, 2 insertions, 14 deletions
diff --git a/scripts/newbitmaps/README b/scripts/newbitmaps/README index c5b7c2ba..d07be4dd 100644 --- a/scripts/newbitmaps/README +++ b/scripts/newbitmaps/README @@ -62,8 +62,6 @@ composited screens as described by the config file. bmpblk_utility -c unknown.yaml bmpblock.bin * Use the gbb_utility to modify the BIOS to contain our new set of bitmaps. - We will need to pad our replacement bmpblock to match the size of the - original. NOTE: These commands are run (as root) on the device under test! @@ -78,18 +76,9 @@ composited screens as described by the config file. flashrom -r bios.bin - Extract the current bmpblock from the BIOS, and see how big it is. - - gbb_utility -g -b oldblob bios.bin - ls -l oldblob - - Pad our bmpblock to the same size (for example, 253568 bytes) - - dd if=bmpblock.bin bs=253568 count=1 of=newblob - Put our bmpblock in our copy of the BIOS - gbb_utility -s newblob bios.bin + gbb_utility -s -b bmpblock.bin bios.bin Reflash the BIOS with the new content @@ -106,5 +95,4 @@ composited screens as described by the config file. bmpblk_utility -y bmpblock.bin - cd /SOME/SCRATCH/DIR - bmpblk_utility -x bmpblock.bin + bmpblk_utility -x -d /SOME/SCRATCH/DIR bmpblock.bin |