[PATCH] ARM: dts: aspeed: Update reserved memory nodes for zaius and witherspoon

Benjamin Herrenschmidt benh at kernel.crashing.org
Tue Feb 21 16:13:40 AEDT 2017


On Tue, 2017-02-21 at 15:15 +1030, Joel Stanley wrote:
> > > The reservation of 64MB is because the hardware is capable of using
> > > 64MB, therefore the host can use that region of memory. We're playing
> > > it safe here by ensuring the BMC doesn't use any of it to avoid any
> > > possibility of the host corrupting BMC memory. This is the most generic
> > > dts for the platform so we've gone with stability over performance.
> > 
> > Is there anything the BMC can do to restrict how big of a memory map the
> > host side of the VGA can open up?  If there isn't we're going to have to
> > allocate this much on all systems because we can't trust the host to
> > "behave".
> 
> Ben and Jeremy have been enhancing the host driver to be smarter. Ben,
> what's the state of play?

That's actually an interesting one ... there is a different mem region
for host VGA and BMC graphics ...

The size it can use as FB (and exposes through PCI) can be selected via
a strapping of the chip.

Ideally, when we have a DT aware uBoot, we could have it adjust that
property based on the value of the strap. I think we can also change it
though, thus we could probably make the SCU code in Linux adjust the
value based on the DT and thus have platform specific DTs reducing the
amount of VRAM exposed to the host.

Cheers,
Ben.


More information about the openbmc mailing list