Re: [U-Boot] [RFC PATCH v1 0/1] Migrate IMAGE_FORMAT_LEGACY to Kconfig

2018-04-20 Thread Tom Rini
On Fri, Apr 20, 2018 at 10:46:00AM +0100, Alex Kiernan wrote: > On Fri, Apr 20, 2018 at 5:23 AM, Alex Kiernan wrote: > > On Thu, Apr 19, 2018 at 8:39 PM, Tom Rini wrote: > >> On Thu, Apr 19, 2018 at 04:52:30AM +, Alex Kiernan wrote: > >>> > >>> On

Re: [U-Boot] [RFC PATCH v1 0/1] Migrate IMAGE_FORMAT_LEGACY to Kconfig

2018-04-20 Thread Alex Kiernan
On Fri, Apr 20, 2018 at 5:23 AM, Alex Kiernan wrote: > On Thu, Apr 19, 2018 at 8:39 PM, Tom Rini wrote: >> On Thu, Apr 19, 2018 at 04:52:30AM +, Alex Kiernan wrote: >>> >>> On the face of it, this is a straightforward moveconfig, but because >>> of

Re: [U-Boot] [RFC PATCH v1 0/1] Migrate IMAGE_FORMAT_LEGACY to Kconfig

2018-04-19 Thread Alex Kiernan
On Thu, Apr 19, 2018 at 8:39 PM, Tom Rini wrote: > On Thu, Apr 19, 2018 at 04:52:30AM +, Alex Kiernan wrote: >> >> On the face of it, this is a straightforward moveconfig, but because >> of how CONFIG_FIT_SIGNATURE, CONFIG_IMAGE_FORMAT_LEGACY and >>

Re: [U-Boot] [RFC PATCH v1 0/1] Migrate IMAGE_FORMAT_LEGACY to Kconfig

2018-04-19 Thread Tom Rini
On Thu, Apr 19, 2018 at 04:52:30AM +, Alex Kiernan wrote: > > On the face of it, this is a straightforward moveconfig, but because > of how CONFIG_FIT_SIGNATURE, CONFIG_IMAGE_FORMAT_LEGACY and > CONFIG_DISABLE_IMAGE_LEGACY interacted when you enabled > CONFIG_FIT_SIGNATURE, you got

[U-Boot] [RFC PATCH v1 0/1] Migrate IMAGE_FORMAT_LEGACY to Kconfig

2018-04-18 Thread Alex Kiernan
On the face of it, this is a straightforward moveconfig, but because of how CONFIG_FIT_SIGNATURE, CONFIG_IMAGE_FORMAT_LEGACY and CONFIG_DISABLE_IMAGE_LEGACY interacted when you enabled CONFIG_FIT_SIGNATURE, you got CONFIG_IMAGE_FORMAT_LEGACY disabled immediately unless you had some way of