Re: [PATCH 2/3] tools: add fdt_add_pubkey

2020-02-11 Thread Simon Glass
Hi Rasmus, On Tue, 11 Feb 2020 at 02:49, Rasmus Villemoes wrote: > > Having to use the -K option to mkimage to populate U-Boot's .dtb with the > public key while signing the kernel FIT image is often a little > awkward. In particular, when using a meta-build system such as > bitbake/Yocto,

Re: [PATCH 2/3] tools: add fdt_add_pubkey

2020-02-11 Thread Alex Kiernan
On Tue, Feb 11, 2020 at 10:22 AM Rasmus Villemoes wrote: > > On 11/02/2020 10.54, Alex Kiernan wrote: > > On Tue, Feb 11, 2020 at 9:49 AM Rasmus Villemoes > > wrote: > >> > >> Having to use the -K option to mkimage to populate U-Boot's .dtb with the > >> public key while signing the kernel FIT

Re: [PATCH 2/3] tools: add fdt_add_pubkey

2020-02-11 Thread Rasmus Villemoes
On 11/02/2020 10.54, Alex Kiernan wrote: > On Tue, Feb 11, 2020 at 9:49 AM Rasmus Villemoes > wrote: >> >> Having to use the -K option to mkimage to populate U-Boot's .dtb with the >> public key while signing the kernel FIT image is often a little >> awkward. In particular, when using a

Re: [PATCH 2/3] tools: add fdt_add_pubkey

2020-02-11 Thread Alex Kiernan
On Tue, Feb 11, 2020 at 9:49 AM Rasmus Villemoes wrote: > > Having to use the -K option to mkimage to populate U-Boot's .dtb with the > public key while signing the kernel FIT image is often a little > awkward. In particular, when using a meta-build system such as > bitbake/Yocto, having the

[PATCH 2/3] tools: add fdt_add_pubkey

2020-02-11 Thread Rasmus Villemoes
Having to use the -K option to mkimage to populate U-Boot's .dtb with the public key while signing the kernel FIT image is often a little awkward. In particular, when using a meta-build system such as bitbake/Yocto, having the tasks of the kernel and U-Boot recipes intertwined, modifying deployed