mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Trent Piepho <trent.piepho@igorinstitute.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] net: Bring up all interfaces before going interactive
Date: Thu, 22 Sep 2022 11:41:15 +0200	[thread overview]
Message-ID: <20220922094115.GK986@pengutronix.de> (raw)
In-Reply-To: <CAMHeXxPJoHO6_eL9sf-_Fu+oqJQv278f9D8RifBkG2YV_yYYmw@mail.gmail.com>

On Tue, Sep 20, 2022 at 02:47:07AM -0700, Trent Piepho wrote:
> On Tue, Sep 20, 2022 at 12:41 AM Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > On Mon, Sep 19, 2022 at 10:20:53AM -0700, Trent Piepho wrote:
> > > On Fri, Sep 16, 2022 at 6:16 AM Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > > >
> > > > We could make the user experience even a bit better by doing this call
> > > > before waiting for the autoboot timeout which then speeds up netboot a
> > > > bit.
> > >
> > > The Linux phy driver almost invariably does not bother to avoid
> > > resetting the network phy when not necessary.  So if network
> > > auto-negotiation is started in barebox, it will be reset and then
> > > restarted shortly after in Linux.  The link auto-negotiation impacts
> > > the LAN's spanning tree if that is in use.
> > >
> > > So there is a drawback, besides the small added boot time to
> > > initialize the network hardware, to adding an unneeded network restart
> > > in Barebox in the case where interactive mode is not entered and
> > > network boot is not used.
> >
> > So is this a vote to only do the autonegotiaton when going interactive
> > in barebox, or a vote to do autonegotiation only when the network is
> > being used in barebox?
> 
> I would vote to only do it when going interactive.

I changed the behaviour accordingly.

> 
> It also seems reasonable to bring the network up quickly when network
> booting, but I think determining if the system will network boot,
> before actually trying to boot, is probably unreasonably difficult to
> do.

I don't know how we could determine if we are going to do a network
boot.
We could do the network initialisation earlier based on some globalvar
like Marco suggested, but currently I do not have enough motivation to
implement it.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2022-09-22 10:08 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 [this message]
2022-09-20  8:22 ` Marco Felsch

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=20220922094115.GK986@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=trent.piepho@igorinstitute.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