mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Marco Felsch <>
To: Sascha Hauer <>
Cc: Barebox List <>
Subject: Re: [PATCH] net: Bring up all interfaces before going interactive
Date: Tue, 20 Sep 2022 10:22:01 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Sascha,

On 22-09-16, Sascha Hauer wrote:
> So far we only bring up network interfaces when we actually need them.
> This means we could be idling in the shell for long and once the user
> decides to do networking he has to wait for the link to be established.
> We can do better: Before going interactive bring up all known network
> interfaces which makes the links established when the user needs them.

can we do that conditional e.g. by using a globalvar? Since this can
cause regression e.g. if your use-case is to boot as fast as possible.


      parent reply	other threads:[~2022-09-20  8:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 12:49 Sascha Hauer
2022-09-16 13:16 ` Sascha Hauer
2022-09-19 17:20   ` Trent Piepho
2022-09-20  7:41     ` Sascha Hauer
2022-09-20  9:47       ` Trent Piepho
2022-09-22  9:41         ` Sascha Hauer
2022-09-20  8:22 ` Marco Felsch [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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