Searched hist:f8f8df6e (Results 1 – 6 of 6) sorted by relevance
| /openbmc/u-boot/tools/binman/etype/ |
| H A D | fmap.py | f8f8df6e Fri Sep 14 05:57:34 CDT 2018 Simon Glass <sjg@chromium.org> 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>
|
| H A D | u_boot_with_ucode_ptr.py | f8f8df6e Fri Sep 14 05:57:34 CDT 2018 Simon Glass <sjg@chromium.org> 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>
|
| /openbmc/u-boot/tools/binman/ |
| H A D | fmap_util.py | f8f8df6e Fri Sep 14 05:57:34 CDT 2018 Simon Glass <sjg@chromium.org> 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>
|
| H A D | bsection.py | f8f8df6e Fri Sep 14 05:57:34 CDT 2018 Simon Glass <sjg@chromium.org> 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>
|
| H A D | entry.py | f8f8df6e Fri Sep 14 05:57:34 CDT 2018 Simon Glass <sjg@chromium.org> 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>
|
| H A D | ftest.py | f8f8df6e Fri Sep 14 05:57:34 CDT 2018 Simon Glass <sjg@chromium.org> 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>
|