diff options
| author | Sam Protsenko <semen.protsenko@linaro.org> | 2018-05-22 02:04:21 +0300 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2018-06-05 10:33:57 -0400 |
| commit | 955575c8dc83a1e4cee69d3ebcc03eef5634aedf (patch) | |
| tree | cf3ad5ace066d40b2d988a70bef8c8b96fa0f7b5 /include/jffs2 | |
| parent | f203a479e7415b539ebcf766591eeafaf481814d (diff) | |
| download | u-boot-955575c8dc83a1e4cee69d3ebcc03eef5634aedf.zip u-boot-955575c8dc83a1e4cee69d3ebcc03eef5634aedf.tar.gz u-boot-955575c8dc83a1e4cee69d3ebcc03eef5634aedf.tar.bz2 | |
disk: efi: Correct backing up the MBR boot code
In commit e163a931af34 ("cmd: gpt: backup boot code before writing MBR")
there was added the procedure for storing old boot code when doing "gpt
write". But instead of storing just backup code, the whole MBR was
stored, and only specific fields were replaced further, keeping
everything else intact. That's obviously not what we want.
Fix the code to actually store only old boot code and zero out
everything else. This fixes next testing case:
=> mmc write $loadaddr 0x0 0x7b
=> gpt write mmc 1 $partitions
In case when $loadaddr address and further memory contains 0xff, the
board was bricked (ROM-code probably didn't like partition entries that
were clobbered with 0xff). With this patch applied, commands above don't
brick the board.
Signed-off-by: Sam Protsenko <semen.protsenko@linaro.org>
Cc: Alejandro Hernandez <ajhernandez@ti.com>
Tested-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Diffstat (limited to 'include/jffs2')
0 files changed, 0 insertions, 0 deletions