Re: [U-Boot] [PATCH] image: fix compiling without CMD_FDT

On Sat, Dec 15, 2018 at 04:00:33PM +0100, Simon Goldschmidt wrote: > Am Sa., 15. Dez. 2018, 15:56 hat Tom Rini geschrieben: > > > On Fri, Dec 14, 2018 at 08:42:18AM +0100, Simon Goldschmidt wrote: > > > > > Booting an image currently sets the environment variable "fdtaddr" > > > by calling into '

Re: [U-Boot] [PATCH] image: fix compiling without CMD_FDT

Am Sa., 15. Dez. 2018, 15:56 hat Tom Rini geschrieben: > On Fri, Dec 14, 2018 at 08:42:18AM +0100, Simon Goldschmidt wrote: > > > Booting an image currently sets the environment variable "fdtaddr" > > by calling into 'cmd/fdt.c'. As a result, linking U-Boot fails if > > CMD_FDT is not enabled. >

Re: [U-Boot] [PATCH] image: fix compiling without CMD_FDT

On Fri, Dec 14, 2018 at 08:42:18AM +0100, Simon Goldschmidt wrote: > Booting an image currently sets the environment variable "fdtaddr" > by calling into 'cmd/fdt.c'. As a result, linking U-Boot fails if > CMD_FDT is not enabled. > > Fix this by adding 'if (CONFIG_IS_ENABLED(CMD_FDT))' to the two

[U-Boot] [PATCH] image: fix compiling without CMD_FDT

Booting an image currently sets the environment variable "fdtaddr" by calling into 'cmd/fdt.c'. As a result, linking U-Boot fails if CMD_FDT is not enabled. Fix this by adding 'if (CONFIG_IS_ENABLED(CMD_FDT))' to the two places where 'set_working_fdt_addr()' is called. Signed-off-by: Simon Goldsc