All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Ross Burton <ross.burton@arm.com>
Cc: openembedded-core@lists.openembedded.org, bill.mills@linaro.org
Subject: Re: [PATCH RFC walnascar 2/3] systemd: always depend on the explicit serial console units
Date: Wed, 23 Apr 2025 14:18:42 +0300	[thread overview]
Message-ID: <aAjMkh6O3bUq1hjS@nuoska> (raw)
In-Reply-To: <20250422190053.3244331-2-ross.burton@arm.com>

Hi,

On Tue, Apr 22, 2025 at 08:00:52PM +0100, Ross Burton wrote:
> The systemd-serialgetty recipe generates explicit units for consoles
> that are defined in SERIAL_CONSOLES, and if that variable is not defined
> then just produces an empty package.
> 
> Even when systemd has been configured to use the getty generator, if
> there are explicit consoles defined then we should respect them.  Don't
> conditionalise the dependency on systemd-serialgetty so that we always
> pull in the explicit consoles.

So all boots of genericarm64 on all HW now wait for the configured
SERIAL_CONSOLES timeouts.

How should that be fixed? Unsetting SERIAL_CONSOLES in genericarm64 machine config?
So systemd-serialgetty is allowed to be machine specific but not systemd itself?

Cheers,

-Mikko


  reply	other threads:[~2025-04-23 11:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 19:00 [PATCH RFC walnascar 1/3] systemd: enable getty generator by default Ross Burton
2025-04-22 19:00 ` [PATCH RFC walnascar 2/3] systemd: always depend on the explicit serial console units Ross Burton
2025-04-23 11:18   ` Mikko Rapeli [this message]
2025-04-23 14:06     ` Ross Burton
     [not found]   ` <1838EE88B5ED2807.22956@lists.openembedded.org>
2025-04-23 13:33     ` [OE-core] " Mikko Rapeli
2025-04-22 19:00 ` [PATCH RFC walnascar 3/3] genericarm64: add ttyPS1 for KV260 Ross Burton
2025-04-23 10:24   ` Mikko Rapeli
2025-04-23 10:26     ` Ross Burton
2025-04-23  1:44 ` [OE-core] [PATCH RFC walnascar 1/3] systemd: enable getty generator by default ChenQi
2025-04-23 10:18 ` Mikko Rapeli
2025-04-23 10:40   ` Ross Burton
2025-04-23 10:55     ` Mikko Rapeli

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=aAjMkh6O3bUq1hjS@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=bill.mills@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.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 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.