On 3/12/22 06:02, Simon Glass wrote:
Hi Marek,
On Fri, 11 Mar 2022 at 19:41, Marek Vasut wrote:
On 3/12/22 03:24, Simon Glass wrote:
Hi Marek,
On Wed, 21 Jul 2021 at 18:05, Marek Vasut wrote:
The current implementation of boot_relocate_fdt() places DT at the
highest usable DRAM address,
Hi Marek,
On Fri, 11 Mar 2022 at 19:41, Marek Vasut wrote:
>
> On 3/12/22 03:24, Simon Glass wrote:
> > Hi Marek,
> >
> > On Wed, 21 Jul 2021 at 18:05, Marek Vasut wrote:
> >>
> >> The current implementation of boot_relocate_fdt() places DT at the
> >> highest usable DRAM address, which is calcu
On 3/12/22 03:24, Simon Glass wrote:
Hi Marek,
On Wed, 21 Jul 2021 at 18:05, Marek Vasut wrote:
The current implementation of boot_relocate_fdt() places DT at the
highest usable DRAM address, which is calculated as:
env_get_bootm_low() + env_get_bootm_mapsize()
which by default becomes gd-
Hi Marek,
On Wed, 21 Jul 2021 at 18:05, Marek Vasut wrote:
>
> The current implementation of boot_relocate_fdt() places DT at the
> highest usable DRAM address, which is calculated as:
> env_get_bootm_low() + env_get_bootm_mapsize()
> which by default becomes gd->ram_base + gd->ram_size.
>
> Sy
The current implementation of boot_relocate_fdt() places DT at the
highest usable DRAM address, which is calculated as:
env_get_bootm_low() + env_get_bootm_mapsize()
which by default becomes gd->ram_base + gd->ram_size.
Systems like i.MX53 can have multiple DRAM banks with gap between them,
e.g.
5 matches
Mail list logo