From mboxrd@z Thu Jan  1 00:00:00 1970
From: Simon Glass <sjg@chromium.org>
Date: Thu, 11 Apr 2019 20:12:05 -0600
Subject: [U-Boot] [PATCH v3 13/13] p2771-0000: Add support for
	framebuffer carveouts
In-Reply-To: <CAPnjgZ0_NQpr2xMF2HX1Co1HDgaFbbDpQTeL+BoVR5y8h8A90A@mail.gmail.com>
References: <20190321181010.27005-1-thierry.reding@gmail.com>
 <20190321181010.27005-14-thierry.reding@gmail.com>
 <CAPnjgZ0_NQpr2xMF2HX1Co1HDgaFbbDpQTeL+BoVR5y8h8A90A@mail.gmail.com>
Message-ID: <CAPnjgZ1uP1AytB=U0BgXyYPY1xDgd5Z17Q3H5R_-vUmi1Ji4tg@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Thierry,

On Fri, 22 Mar 2019 at 01:53, Simon Glass <sjg@chromium.org> wrote:
>
> On Fri, 22 Mar 2019 at 02:10, Thierry Reding <thierry.reding@gmail.com> wrote:
> >
> > From: Thierry Reding <treding@nvidia.com>
> >
> > If early firmware initialized the display hardware and the display
> > controllers are scanning out a framebuffer (e.g. a splash screen), make
> > sure to pass information about the memory location of that framebuffer
> > to the kernel before booting to avoid the kernel from using that memory
> > for the buddy allocator.
> >
> > This same mechanism can also be used in the kernel to set up early SMMU
> > mappings and avoid SMMU faults caused by the display controller reading
> > from memory for which it has no mapping.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> >  board/nvidia/p2771-0000/p2771-0000.c | 66 ++++++++++++++++++++++++++--
> >  1 file changed, 62 insertions(+), 4 deletions(-)
> >
>
> Reviewed-by: Simon Glass <sjg@chromium.org>

This doesn't apply for me. Please can you resend it?

Regards,
Simon