ng
'printenv'.
The flash probe itself should always take the same (rather short) amount
of time. Reading a Linux kernel from flash is slower than reading a small
environment block, though, because the kernel is much bigger.
Hope that helps,
Thomas Betker
Hello Shabbir:
> Yes. FSBL is encrypted and is used to start u-boot.
> My problem is, by default since cortex-a9 is trustzone compliant it
boots
> in secure state, but i want to switch dynamically to non-secure state by
> calling smc #0 in start.S of my u-boot. Since I have successfully set up
>
e
as the unencrypted binary.
My guess would be that either your FSBL is not encrypted, or something
else went wrong when generating and installing the boot image.
Best regards,
Thomas Betker
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hello Simon:
> > run_command() returns 0 for success, 1 for failure. Fix places which
> > assume that failure is indicated by a negative return code.
> >
> > Signed-off-by: Thomas Betker
>
> This has come through fine to patchwork - it may have been your
>
un_command() invocations in
general.
Best regards,
Thomas Betker
Thomas Betker (3):
Check run_command() return code properly
Add run_command_repeatable()
Use run_command_repeatable()
arch/arm/cpu/arm926ejs/kirkwood/cpu.c | 2 +-
board/gdsys/p1022/controlcenterd.c| 6 +-
co
Replace run_command() by run_command_repeatable() in places which
depend on the return code to indicate repeatability.
Signed-off-by: Thomas Betker
---
common/cli_simple.c | 2 +-
common/cmd_bedbug.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/common/cli_simple.c b
run_command() returns 0 on success and 1 on error. However, there are some
invocations which expect 0 or 1 for success (not repeatable or repeatable)
and -1 for error; add run_command_repeatable() for this purpose.
Signed-off-by: Thomas Betker
---
common/cli.c | 24
run_command() returns 0 for success, 1 for failure. Fix places which
assume that failure is indicated by a negative return code.
Signed-off-by: Thomas Betker
---
arch/arm/cpu/arm926ejs/kirkwood/cpu.c | 2 +-
board/gdsys/p1022/controlcenterd.c| 6 +-
common/cmd_bootm.c
From: Thomas Betker
The intent of these patches is to get command repeat to work again. The
issue is that run_command() returns 0 on success, 1 on error. In order
to get command repeat to work, we need a variant which returns -1 on
error and 0/1 (non-repeatable/repeatable) on succcess, the
From: Thomas Betker
run_command() returns 0 for success, 1 for failure. Fix places which
assume that failure is indicated by a negative return code.
Signed-off-by: Thomas Betker
---
arch/arm/cpu/arm926ejs/kirkwood/cpu.c |2 +-
board/gdsys/p1022/controlcenterd.c|6 +-
common
From: Thomas Betker
Replace run_command() by run_command_repeatable() in places which
depend on the return code to indicate repeatability.
Signed-off-by: Thomas Betker
---
common/cli_simple.c |2 +-
common/cmd_bedbug.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff
From: Thomas Betker
run_command() returns 0 on success and 1 on error. However, there are some
invocations which expect 0 or 1 for success (not repeatable or repeatable)
and -1 for error; add run_command_repeatable() for this purpose.
Signed-off-by: Thomas Betker
---
common/cli.c | 24
Hello Simon:
> Are you planning to work on a patch?
Yes, I am; I hope to send something out tonight. Sorry for the delay!
Best regards,
Thomas
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
lways returns 0 for success, 1 for failure.]
Any thoughts on this? I am willing to prepare a patch, but I certainly
don't mind if this is handled by somebody else who is deeper into u-boot
than me.
Best regards,
Thomas Betker
___
U-Boot
14 matches
Mail list logo
