On Wed, 14 Aug 2019 at 18:42, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> I'm not sure I agree with this.
> We are meant to work on embedded systems and 256MB should be enough to
> let us bring up X under qemu.
> I'm fine with some sdk/ptest images having more memory, that makes
> sense but 256MB not allowing X under qemu seems rather poor.

I poked a bit more at this. The main difference between vmware emulated
hardware and std emulated hardware is that X uses the standard 2D
framebuffer interface for the former, and the full 3D stack for the latter
(via use of glamor: https://www.freedesktop.org/wiki/Software/Glamor/). The
3D stack (mesa and friends) is what causes the memory usage to swell.

It is possible to disable this behaviour and enforce framebuffer usage (see
'man modesetting'), and I have verified that the RAM usage drops to similar
levels as vmware, but that is not the upstream default; they have more or
less obsoleted 2D drivers and are defaulting to 3D rendering nowadays. I'd
rather follow that.

Openembedded-core mailing list

Reply via email to