From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <rs@ti.com>, <richard.purdie@linuxfoundation.org>,
<ross.burton@arm.com>, <alex@linutronix.de>,
<otavio@ossystems.com.br>, <kexin.hao@windriver.com>,
<afd@ti.com>, <detheridge@ti.com>, <denis@denix.org>,
<reatmon@ti.com>
Cc: <openembedded-core@lists.openembedded.org>, <vijayp@ti.com>
Subject: Re: [oe-core][PATCHv2 0/3] Display manager proposal for x11 and wayland
Date: Tue, 06 May 2025 09:47:46 +0200 [thread overview]
Message-ID: <D9OWUBHID8JT.3FJEJAXYPMT2W@bootlin.com> (raw)
In-Reply-To: <20250505224801.3181046-1-rs@ti.com>
On Tue May 6, 2025 at 12:47 AM CEST, rs wrote:
> From: Randolph Sapp <rs@ti.com>
>
> We've recently run into some issues with weston-init attempting to start
> Weston prior to all drm devices being registered. There's not really a
> good, scriptable mechanism to listen in to device registration events
> that works with the existing weston-init package. Well, at least one
> that doesn't involve polling files or introducing more dependency on the
> init system being used.
>
> I also see there is also a lot of scripting around starting X11,
> xserver-nodm-init, that (from my limited review) should experience the
> same issue.
>
> I'd like to introduce the following display manager for oe-core, emptty
> [1]. This display manager is, as described upstream, a "Dead simple CLI
> Display Manager on TTY". It supports both x11 and wayland sessions, with
> togglable build parameters to completely remove x11 and pam
> dependencies. It's licensed MIT, which shouldn't be an issue for any
> users. (It is written in Go, if you have opinions about that.)
>
> With this, both weston-init and the xserver-nodm-init packages can be
> re-tuned to leverage this display manager and simply add a user and
> emptty config for an autologin session. This can resolve the current
> behavior across init systems without additional scripting, and move some
> development out of this layer.
>
> This lists myself as a maintainer of emptty as well as xserver-nodm-init and
> xuser-account since these are currently unassigned and I've reworked them
> significantly here.
>
> Sorry for the delay on this series. I found a few bugs in emptty that I wanted
> to address before submitting this officially.
>
> [1] https://github.com/tvrzna/emptty
>
> v2:
> - Address spelling issues in commit messages
> - Attempt to resolve some test related issues with weston
> - Add additional logs to X11 related tests
Hi Randolph,
Thanks for the v2.
However, it looks like we still have an error with the emptty
dependency:
ERROR: Nothing RPROVIDES 'emptty' (but /srv/pokybuild/yocto-worker/qemux86-64-x32/build/meta/recipes-graphics/x11-common/xserver-nodm-init_3.0.bb RDEPENDS on or otherwise requires it)
emptty was skipped: incompatible with host x86_64-poky-linux-gnux32 (not in COMPATIBLE_HOST)
https://autobuilder.yoctoproject.org/valkyrie/#/builders/11/builds/1512
Can you have a look at the issue please?
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-05-06 7:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 22:47 [oe-core][PATCHv2 0/3] Display manager proposal for x11 and wayland rs
2025-05-05 22:47 ` [oe-core][PATCHv2 1/3] emptty: add version 0.14.0 rs
2025-05-05 22:48 ` [oe-core][PATCHv2 2/3] weston-init: convert to virtual-emptty-conf rs
2025-05-05 22:48 ` [oe-core][PATCHv2 3/3] xserver-nodm-init: " rs
2025-05-06 7:47 ` Mathieu Dubois-Briand [this message]
2025-05-06 23:03 ` [oe-core][PATCHv2 0/3] Display manager proposal for x11 and wayland Randolph Sapp
2025-05-07 13:37 ` Alexander Kanavin
2025-05-07 20:42 ` Randolph Sapp
[not found] ` <183D59758C0F13FA.9842@lists.openembedded.org>
2025-05-08 20:39 ` Randolph Sapp
2025-05-09 8:27 ` Richard Purdie
2025-05-13 6:15 ` Mathieu Dubois-Briand
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=D9OWUBHID8JT.3FJEJAXYPMT2W@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=afd@ti.com \
--cc=alex@linutronix.de \
--cc=denis@denix.org \
--cc=detheridge@ti.com \
--cc=kexin.hao@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=reatmon@ti.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@arm.com \
--cc=rs@ti.com \
--cc=vijayp@ti.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox