Hi Simon,
Thanks and to Heiko also.
Mike
On 09/05/2014 11:54 PM, Simon Glass wrote:
Hi,
On 6 May 2014 00:38, Heiko Schocher h...@denx.de wrote:
Hello Mike,
Am 05.05.2014 16:27, schrieb Mike Pearce:
Please help as I am confused.
I implemented verified boot on 2014.04 using
Hi,
On 6 May 2014 00:38, Heiko Schocher h...@denx.de wrote:
Hello Mike,
Am 05.05.2014 16:27, schrieb Mike Pearce:
Please help as I am confused.
I implemented verified boot on 2014.04 using CONFIG_OF_SEPARATE and it
works fine with FIT images. However it still boots the resident legacy
Hello Mike,
Am 05.05.2014 16:27, schrieb Mike Pearce:
Please help as I am confused.
I implemented verified boot on 2014.04 using CONFIG_OF_SEPARATE and it
works fine with FIT images. However it still boots the resident legacy
kernal that has not been signed.
This means that anyone wishing to
Please help as I am confused.
I implemented verified boot on 2014.04 using CONFIG_OF_SEPARATE and it
works fine with FIT images. However it still boots the resident legacy
kernal that has not been signed.
This means that anyone wishing to circumvent the signed hash can do so by
replacing the
4 matches
Mail list logo