On Fri, Sep 21, 2018 at 1:43 PM Wolfgang Denk wrote:
>
> Dear Alex,
>
> In message <20180918081013.26660-1-alex.kier...@gmail.com> you wrote:
> > When the image which bootm is given can't be booted, call panic with
> > the error message rather than printf/hang so that we can recover from
> >
Dear Alex,
In message <20180918081013.26660-1-alex.kier...@gmail.com> you wrote:
> When the image which bootm is given can't be booted, call panic with
> the error message rather than printf/hang so that we can recover from
> broken images via a bootcount mechanism. If hang on failure is still
>
On 09/18/2018 02:10 AM, Alex Kiernan wrote:
When the image which bootm is given can't be booted, call panic with
the error message rather than printf/hang so that we can recover from
broken images via a bootcount mechanism. If hang on failure is still
required then CONFIG_PANIC_HANG can still be
When the image which bootm is given can't be booted, call panic with
the error message rather than printf/hang so that we can recover from
broken images via a bootcount mechanism. If hang on failure is still
required then CONFIG_PANIC_HANG can still be enabled.
Signed-off-by: Alex Kiernan
---
4 matches
Mail list logo