From: Denys Dmytriyenko <denis@denix.org>
To: sebastian.krahl@lacon.de
Cc: meta-ti@lists.yoctoproject.org, rs@ti.com
Subject: Re: [meta-ti] core-image-sato scarthgap beaglebone x11 startup error
Date: Tue, 6 May 2025 12:29:44 -0400 [thread overview]
Message-ID: <20250506162944.GC18383@denix.org> (raw)
In-Reply-To: <4weC.1746543468071238638.sYyH@lists.yoctoproject.org>
+ 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.
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.
>
> 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
next prev parent reply other threads:[~2025-05-06 16:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 14:57 core-image-sato scarthgap beaglebone x11 startup error Sebastian
2025-05-06 16:29 ` Denys Dmytriyenko [this message]
2025-05-06 21:55 ` [meta-ti] " Randolph Sapp
2025-05-06 22:53 ` Denys Dmytriyenko
2025-05-07 5:40 ` Sebastian
2025-05-08 18:33 ` [meta-ti] " Randolph Sapp
2025-05-08 19:13 ` Denys Dmytriyenko
2025-05-08 20:37 ` Sebastian
2025-05-13 11:05 ` Sebastian
2025-05-21 13:37 ` Sebastian
2025-05-22 13:30 ` [meta-ti] " Andrew Davis
2025-05-27 7:59 ` Sebastian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250506162944.GC18383@denix.org \
--to=denis@denix.org \
--cc=meta-ti@lists.yoctoproject.org \
--cc=rs@ti.com \
--cc=sebastian.krahl@lacon.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.