24 Jul, 2019

1 commit


18 Jul, 2019

1 commit


17 Jul, 2019

14 commits


13 Jul, 2019

1 commit

  • The USE_TINY_PRINTF symbol only changes things within SPL and TPL
    builds, so make it depend on that support. Next, make it default as
    within these cases we should rarely have need of more advanced print
    formats outside of the debug context.

    To do this, in a few cases we need to correct our Kconfig dependencies
    as we had cases of non-SPL targets select'ing this symbol. Finally, in
    the case of a few boards we really do need the full printf
    functionality.

    Signed-off-by: Tom Rini

    Tom Rini
     

11 Jul, 2019

5 commits

  • There is no good reason to limit the trace buffer to 2GiB on a 64bit
    system. Adjust the types of the relevant parameters.

    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Simon Glass

    Heinrich Schuchardt
     
  • Up to now we had hard coded values for the call depth up to which trace
    records are created: 200 for early tracing, 15 thereafter. UEFI
    applications reach a call depth of 80 or above.

    Provide customizing settings for the call trace depth limit and the early
    call trace depth limit. Use the old values as defaults.

    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Simon Glass

    Heinrich Schuchardt
     
  • An UEFI application may change the value of the register that gd lives in.
    But some of our functions like get_ticks() access this register. So we
    have to set the gd register to the U-Boot value when entering a trace
    point and set it back to the application value when exiting the trace
    point.

    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Simon Glass

    Heinrich Schuchardt
     
  • Free the memory allocated to store the test FDT upon test completion to
    avoid leaking the memory. We don't bother cleaning up on test failure
    since the code is broken in that case and should be fixed, in which case
    the leak would also go away.

    Reported-by: Tom Rini
    Suggested-by: Heinrich Schuchardt
    Signed-off-by: Thierry Reding
    Reviewed-by: Simon Glass

    Thierry Reding
     
  • It doesn't make a lot of sense to hang on sandbox when hang() is called,
    since the only way out is Ctrl-C. In fact, Ctrl-C does not work if the
    terminal is in raw mode, which it will be if the command-line has not been
    reached yet. In that case, Ctrl-Z / kill -9 must be used, which is not
    very friendly.

    Avoid all of this by quiting when hang() is called.

    Signed-off-by: Simon Glass

    Simon Glass
     

07 Jul, 2019

13 commits


22 Jun, 2019

1 commit


21 Jun, 2019

4 commits