From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Barbier, Renaud" <renaud.barbier@abaco.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: barebox:ubi attach time
Date: Mon, 14 Sep 2020 15:17:01 +0200 [thread overview]
Message-ID: <20200914131701.GT4498@pengutronix.de> (raw)
In-Reply-To: <MN2PR16MB313561D8BE9DFFB84707FA49912E0@MN2PR16MB3135.namprd16.prod.outlook.com>
On Tue, Sep 01, 2020 at 10:31:36AM +0000, Barbier, Renaud wrote:
>
>
> >
> > Hi Renaud,
> >
> > On Fri, Aug 14, 2020 at 01:49:25PM +0000, Barbier, Renaud wrote:
> > > Just to see if somebody has the following problem:
> > >
> > > We have PPC or ARM platforms with a NOR containing barebox and a UBI
> > > volume with an ITB image. The File system is on NAND.
> > >
> > > If I boot the system, ubiattach and mount the NOR volume, then detach.
> > > On reboot it takes more time for barebox to ubiattach the NOR boot
> > > volume. I have noticed that with on 2019.07 barebox branch and
> > > 2020.03.
> > >
> > > I ubidetach the volume from barebox then boot time is restored.
> >
> > Are you using fastmap?
> [Barbier, Renaud]
> Indeed. We do.
In that case watch out for messages whether or not the volume is
attached with fastmap. It looks like for whatever reason barebox can't
use the fastmap and thus probing takes longer.
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2020-09-14 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 13:49 Barbier, Renaud
2020-08-17 4:12 ` Sascha Hauer
2020-09-01 10:31 ` Barbier, Renaud
2020-09-14 13:17 ` Sascha Hauer [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:
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=20200914131701.GT4498@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=renaud.barbier@abaco.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