Re: [PATCH] configs: powerpc: Don't set CONFIG_ENV_ADDR for T2080RDB_SPIFLASH

2020-09-04 Thread Tom Rini
On Fri, Sep 04, 2020 at 06:01:44PM +1200, Chris Packham wrote: > On Fri, 4 Sep 2020, 12:16 AM Tom Rini, wrote: > > > On Thu, Sep 03, 2020 at 12:02:06PM +1200, Chris Packham wrote: > > > > > Setting CONFIG_ENV_ADDR to something other than 0 stops gd->env_addr > > > from being allocated dynamically

Re: [PATCH] configs: powerpc: Don't set CONFIG_ENV_ADDR for T2080RDB_SPIFLASH

2020-09-03 Thread Chris Packham
On Fri, 4 Sep 2020, 12:16 AM Tom Rini, wrote: > On Thu, Sep 03, 2020 at 12:02:06PM +1200, Chris Packham wrote: > > > Setting CONFIG_ENV_ADDR to something other than 0 stops gd->env_addr > > from being allocated dynamically. When the environment is in SPI we need > > it to be allocated as we can't

Re: [PATCH] configs: powerpc: Don't set CONFIG_ENV_ADDR for T2080RDB_SPIFLASH

2020-09-03 Thread Tom Rini
On Thu, Sep 03, 2020 at 12:02:06PM +1200, Chris Packham wrote: > Setting CONFIG_ENV_ADDR to something other than 0 stops gd->env_addr > from being allocated dynamically. When the environment is in SPI we need > it to be allocated as we can't use a direct memory mapped address. > > Signed-off-by:

[PATCH] configs: powerpc: Don't set CONFIG_ENV_ADDR for T2080RDB_SPIFLASH

2020-09-02 Thread Chris Packham
Setting CONFIG_ENV_ADDR to something other than 0 stops gd->env_addr from being allocated dynamically. When the environment is in SPI we need it to be allocated as we can't use a direct memory mapped address. Signed-off-by: Chris Packham --- configs/T2080RDB_SPIFLASH_defconfig | 1 - 1 file cha