On Thu, Aug 20, 2020 at 8:11 AM Tom Rini wrote:
>
> On Thu, Aug 20, 2020 at 07:42:13AM -0500, Adam Ford wrote:
> > On Thu, Aug 20, 2020 at 7:17 AM Tom Rini wrote:
> > >
> > > On Wed, Aug 19, 2020 at 02:11:08PM -0500, Adam Ford wrote:
> > >
> > > > The loading address is too close to the kernel
On Thu, Aug 20, 2020 at 07:42:13AM -0500, Adam Ford wrote:
> On Thu, Aug 20, 2020 at 7:17 AM Tom Rini wrote:
> >
> > On Wed, Aug 19, 2020 at 02:11:08PM -0500, Adam Ford wrote:
> >
> > > The loading address is too close to the kernel address, so newer kernels
> > > may overlap memory space, so
On Thu, Aug 20, 2020 at 7:17 AM Tom Rini wrote:
>
> On Wed, Aug 19, 2020 at 02:11:08PM -0500, Adam Ford wrote:
>
> > The loading address is too close to the kernel address, so newer kernels
> > may overlap memory space, so loading the device tree may corrupt zImage.
> >
> > This patch moves the
On Wed, Aug 19, 2020 at 02:11:08PM -0500, Adam Ford wrote:
> The loading address is too close to the kernel address, so newer kernels
> may overlap memory space, so loading the device tree may corrupt zImage.
>
> This patch moves the fdt_addr_r to 0x1800 which is also consistent
> with some
The loading address is too close to the kernel address, so newer kernels
may overlap memory space, so loading the device tree may corrupt zImage.
This patch moves the fdt_addr_r to 0x1800 which is also consistent
with some other i.MX6Q boards.
Signed-off-by: Adam Ford
diff --git
5 matches
Mail list logo