<div dir="ltr">Maybe we should drop x11 from default DISTRO_FEATURES :)<div><br></div><div>Will resolve the memory consumption and image size.</div><div><br></div><div>Well the image size isn't much different, I was just surprised to see libx11 being included even in core-image-minimal (because systemd -> dbus -> libx11: "dbus.do_package" -> "libx11.do_packagedata"), but in the end the difference in ext4 was only 2MB (61MB/63MB), caused by following 4 packages:</div><div>libx11-6 core2-64 1:1.6.8-r0.0<br></div><div>libxau6 core2-64 1:1.0.9-r0.15<br>libxcb1 core2-64 1.13.1-r0.15<br>libxdmcp6 core2-64 1:1.1.3-r0.15</div><div><br></div><div>so I guess embedded no longer have neither small ram nor small flash.</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 15, 2019 at 6:20 PM Alexander Kanavin <<a href="mailto:alex.kanavin@gmail.com" target="_blank">alex.kanavin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Wed, 14 Aug 2019 at 18:42, Richard Purdie <<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I'm not sure I agree with this.<br>
<br>
We are meant to work on embedded systems and 256MB should be enough to<br>
let us bring up X under qemu.<br>
<br>
I'm fine with some sdk/ptest images having more memory, that makes<br>
sense but 256MB not allowing X under qemu seems rather poor.<br></blockquote><div><br></div><div>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: <a href="https://www.freedesktop.org/wiki/Software/Glamor/" target="_blank">https://www.freedesktop.org/wiki/Software/Glamor/</a>). The 3D stack (mesa and friends) is what causes the memory usage to swell.<br></div><div><br></div><div>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.<br></div><div><br></div><div>Alex<br></div><div><br></div><div><br></div></div></div>
-- <br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote></div>