binman: Correct fmap output on x86
authorSimon Glass <sjg@chromium.org>
Fri, 14 Sep 2018 10:57:34 +0000 (04:57 -0600)
committerSimon Glass <sjg@chromium.org>
Sat, 29 Sep 2018 17:49:35 +0000 (11:49 -0600)
commitf8f8df6eb870b53e025aa447f8d40cd2ce2a77f6
tree855c9fc502d44854dd969a1ea671088c09f089a9
parent08723a7abbc7e28b22d18684faf5142fc6f155e8
binman: Correct fmap output on x86

Normally x86 platforms use the end-at-4gb option. This currently produces
an FMAP with positions which have a large offset. The use of end-at-4gb is
a useful convenience within binman, but we don't really want to export
a map with these offsets.

Fix this by subtracting the 'skip at start' parameter.

Also put the code which convers names to fmap format, for clarity.

Signed-off-by: Simon Glass <sjg@chromium.org>
tools/binman/bsection.py
tools/binman/entry.py
tools/binman/etype/fmap.py
tools/binman/etype/u_boot_with_ucode_ptr.py
tools/binman/fmap_util.py
tools/binman/ftest.py
tools/binman/test/94_fmap_x86.dts [new file with mode: 0644]
tools/binman/test/95_fmap_x86_section.dts [new file with mode: 0644]