From: Ross Burton <ross.burton@arm.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/2] systemd-serialgetty: add comments explaining use
Date: Thu, 30 Jan 2025 17:59:00 +0000 [thread overview]
Message-ID: <20250130175901.938043-1-ross.burton@arm.com> (raw)
Add some comments to clarify exactly what this recipe is for.
Signed-off-by: Ross Burton <ross.burton@arm.com>
---
meta/recipes-core/systemd/systemd-serialgetty.bb | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/systemd/systemd-serialgetty.bb b/meta/recipes-core/systemd/systemd-serialgetty.bb
index 9035b8c335a..7b525b10f0c 100644
--- a/meta/recipes-core/systemd/systemd-serialgetty.bb
+++ b/meta/recipes-core/systemd/systemd-serialgetty.bb
@@ -1,8 +1,13 @@
-SUMMARY = "Serial terminal support for systemd"
+SUMMARY = "Serial terminal support for systemd (using SERIAL_CONSOLES)"
HOMEPAGE = "https://www.freedesktop.org/wiki/Software/systemd/"
LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/GPL-2.0-only;md5=801f80980d171dd6425610833a22dbe6"
+# Note that this recipe explicitly creates a serial-getty@ service for every tty
+# in SERIAL_CONSOLES. This is typically not always needed with systemd as it
+# will probe at boot and generate getty instances for any active consoles as
+# required. This recipe (enabled via disabling serial-getty-generator in systemd)
+# should only be used if the generator is not appropriate.
SERIAL_CONSOLES ?= "115200;ttyS0"
SERIAL_TERM ?= "linux"
--
2.43.0
next reply other threads:[~2025-01-30 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 17:59 Ross Burton [this message]
2025-01-30 17:59 ` [PATCH 2/2] systemd: use getty generators by default Ross Burton
2025-01-31 7:25 ` [OE-core] " Mikko Rapeli
2025-01-31 16:21 ` Ross Burton
2025-01-31 14:16 ` [OE-core] [PATCH 1/2] systemd-serialgetty: add comments explaining use Mathieu Dubois-Briand
2025-01-31 15:06 ` Ross Burton
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=20250130175901.938043-1-ross.burton@arm.com \
--to=ross.burton@arm.com \
--cc=openembedded-core@lists.openembedded.org \
/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