diff options
author | Aaron Durbin <adurbin@chromium.org> | 2014-03-26 22:57:55 -0500 |
---|---|---|
committer | Aaron Durbin <adurbin@google.com> | 2014-03-28 14:40:53 +0100 |
commit | 4f3bb801edffb27e7e52c297cf6cf5dc4ad22a95 (patch) | |
tree | bdbcafe715bbee133b05151587e09c81867c598f /src/mainboard/google/slippy | |
parent | 2164831671aab4181bc7ba1d57237c4f782864e8 (diff) |
cbfstool: provide structure to linux payload builder
This change started with tracking down a bug where the trampoline
size was not being taken into account for sizing the output buffer
leading to a heap corruption. I was having a hard time keeping
track of what num_segments actually tracked as well as what parts
were being placed in the output buffer. Here's my attempt at
hopefully providing more clarity.
This change doesn't crash when adding a bzImage:
$ dd if=/dev/zero of=bb.bin bs=64 count=1
$ ./cbfstool tmp.rom create -s 4M -B bb.bin -m x86 -a 64
$ ./cbfstool tmp.rom add-payload -f ~/Downloads/bzImage -C "1" -n
"fallback"/payload
Change-Id: Ib1de1ddfec3c7102facffc5815c52b340fcdc628
Signed-off-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-on: http://review.coreboot.org/5408
Tested-by: build bot (Jenkins)
Reviewed-by: Edward O'Callaghan <eocallaghan@alterapraxis.com>
Reviewed-by: Marc Jones <marc.jones@se-eng.com>
Diffstat (limited to 'src/mainboard/google/slippy')
0 files changed, 0 insertions, 0 deletions