microblaze: Clear print messages for DTB passing via r7
It is necessary to zeroed r7 when r7 points to bad dtb - this caused that we have correct messages about compiled-in dtb or passing via r7 Signed-off-by: Michal Simek <monstr@monstr.eu>
This commit is contained in:
parent
a69cb8c466
commit
ea3fd1466f
|
@ -62,7 +62,10 @@ ENTRY(_start)
|
||||||
beqi r7, no_fdt_arg /* NULL pointer? don't copy */
|
beqi r7, no_fdt_arg /* NULL pointer? don't copy */
|
||||||
lw r11, r0, r7 /* Does r7 point to a */
|
lw r11, r0, r7 /* Does r7 point to a */
|
||||||
rsubi r11, r11, OF_DT_HEADER /* valid FDT? */
|
rsubi r11, r11, OF_DT_HEADER /* valid FDT? */
|
||||||
|
beqi r11, _prepare_copy_fdt
|
||||||
|
or r7, r0, r0 /* clear R7 when not valid DTB */
|
||||||
bnei r11, no_fdt_arg /* No - get out of here */
|
bnei r11, no_fdt_arg /* No - get out of here */
|
||||||
|
_prepare_copy_fdt:
|
||||||
or r11, r0, r0 /* incremment */
|
or r11, r0, r0 /* incremment */
|
||||||
ori r4, r0, TOPHYS(_fdt_start)
|
ori r4, r0, TOPHYS(_fdt_start)
|
||||||
ori r3, r0, (0x4000 - 4)
|
ori r3, r0, (0x4000 - 4)
|
||||||
|
|
Loading…
Reference in New Issue