Re: [meta-ti] core-image-sato scarthgap beaglebone x11 startup error

[Randolph Sapp <rs@ti.com>]

On Tue May 6, 2025 at 11:29 AM CDT, Denys Dmytriyenko wrote:
> + Randolph
>
> Unlike yocto-bsp, which uses vanilla mainline kernel with unaccelerated 
> framebuffer, meta-ti by default enables accelerated graphics with out-of-tree 
> drivers and user-space GLES libraries - SGX in case of Beaglebone and AM335x.
>
> When meta-ti migrated from 6.1 kernel to 6.6, I believe X11 support was 
> dropped. It should still be possible to fall back to unaccelerated framebuffer 
> and get X11 working, but that's not something that is configured nor tested in 
> meta-ti.

This was not a result of a kernel change, it was due to a Yocto lts version
change. A lot of layers use a common PACKAGECONFIG pattern that configures
packages to use Desktop GL instead of GLES when opengl and x11 distro features
are enabled. Arago took a hard stance that we will disable x11 to avoid
reconfiguring numerous packages for partial acceleration under x11. Users can
try it, but they will need to be careful when configuring things.

> On Tue, May 06, 2025 at 07:57:48AM -0700, Sebastian via lists.yoctoproject.org wrote:
>> I've tested meta-ti for kirkstone the xserver starts up correctly into an X 
>> session.
>> 
>> With meta-ti for scarthgap it fails. As it looks for a /dev/fb device which 
>> is not present.

Can you elaborate on this? Missing framebuffer devices is actually a display
controller related issue. If you have a splash screen then some fb device is
being registered. What device is this for?
 
>> Aside of this, with kirkstone and scarthgap in yocto-bsp and 
>> beaglebone-yocto it works in both cases.
>> 
>> The framebuffer is filled up by the splash screen also in powering down.
>> 
>> What am I missing?
>> 
>> What info to supply?
>> 
>> Regards,
>> 
>> Sebastian