diff options
author | Martin Roth <martinroth@chromium.org> | 2016-11-08 09:55:01 -0700 |
---|---|---|
committer | Martin Roth <martinroth@google.com> | 2016-11-10 00:24:46 +0100 |
commit | 60f1551461a16cf1b6dc294f715a22748dcb501c (patch) | |
tree | 764605db4dda03115667dd021f02fe6f2afdabc2 /src/lib/memmove.c | |
parent | 21fdd8d0b2206be85dd920e94fb9657a22ab5226 (diff) |
util/amdfwtool: Update with ROM size command line parameter
Previously, the ROM size was passed into amdfwtool solely as a #define,
meaning that all boards built with the tool would assume the same size
ROM. This became a problem when the default rom for abuild was updated
to be a board with a 256KB ROM.
The temporary solution was to build amdfwtool individually for each
board that needed it. This replaces that workaround by allowing the
ROM size to be passed in as a command line parameter.
- Add the -f | --flashsize option to accept a hex value for the ROM
size.
- Add checks to make sure the ROM size supplied is large enough.
- Because the ROM size is not hardcoded, it needs to be passed to
various functions.
Signed-off-by: Martin Roth <martinroth@chromium.org>
Change-Id: I0ca69cbba54797e0387a6e85935767b4136ef615
Reviewed-on: https://review.coreboot.org/17321
Tested-by: build bot (Jenkins)
Reviewed-by: Marshall Dawson <marshalldawson3rd@gmail.com>
Diffstat (limited to 'src/lib/memmove.c')
0 files changed, 0 insertions, 0 deletions