On Mon, Sep 07, 2020 at 10:37:35AM +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:
On Tue, Sep 22, 2020 at 09:12:26AM +1200, Chris Packham wrote:
> Hi Tom,
>
> On Mon, Sep 7, 2020 at 10:37 AM 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
Hi Tom,
On Mon, Sep 7, 2020 at 10:37 AM 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:
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
---
Changes in v2:
- Update the other SPIFLASH_defconfigs
4 matches
Mail list logo