From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: linux-mtd@lists.infradead.org,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Sascha Hauer <kernel@pengutronix.de>
Subject: Re: imx27: Unsupported ECC algorithm
Date: Tue, 13 Oct 2020 19:36:52 +0200 [thread overview]
Message-ID: <20201013193652.0c535c7c@xps13> (raw)
In-Reply-To: <622a62489fa717fe8a94cd2e9cdf3d906da5141f.camel@pengutronix.de>
Hi Lucas,
Lucas Stach <l.stach@pengutronix.de> wrote on Tue, 13 Oct 2020 19:14:21
+0200:
> On Do, 2020-10-01 at 18:39 -0300, Fabio Estevam wrote:
> > Hi Miquel,
> >
> > On Wed, Sep 30, 2020 at 11:58 AM Miquel Raynal
> > <miquel.raynal@bootlin.com> wrote:
> >
> > > I found a board (NTC C.H.I.P, sun5i R8 SoC) with a parallel NAND.
> > >
> > > with the same DT properties but a different NAND controller driver I
> > > could not reproduce the issue.
> > >
> > > However, I did tried with soft BCH and I found a related error which I
> > > just fixed. I also got a bug report from Intel's robot which I also
> > > fixed. Perhaps what you see is related (still around this ->total entry
> > > not being set at the right moment at probe time).
> > >
> > > If tomorrow's report still returns an error, we will need someone
> > > to get physical access to the device to add debugging code and track
> > > down the failure.
> >
> > The linux-next 20201001 results from the kernelci Pengutronix lab did
> > not show up, so let's wait to see the imx27 boot log to be back online
> > again.
>
> Just a heads up: our lab was broken for some time due to a local issue.
> It's now back to working and the backlog of jobs is being executed on
> the boards right now, so results should show up in the near furture.
Understood. Based on the previous reports shared by Fabio I tried to
forge the html links toward more recent reports but it always failed,
now I know why :)
Cheers,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-10-13 17:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 13:49 imx27: Unsupported ECC algorithm Fabio Estevam
2020-09-17 16:13 ` Miquel Raynal
2020-09-17 16:45 ` Miquel Raynal
2020-09-17 17:12 ` Fabio Estevam
2020-09-21 9:40 ` Sascha Hauer
2020-09-28 15:20 ` Miquel Raynal
2020-09-29 11:39 ` Fabio Estevam
2020-09-29 16:31 ` Fabio Estevam
2020-09-29 17:46 ` Miquel Raynal
2020-09-30 14:58 ` Miquel Raynal
2020-10-01 21:39 ` Fabio Estevam
2020-10-13 17:14 ` Lucas Stach
2020-10-13 17:36 ` Miquel Raynal [this message]
2020-10-14 12:23 ` Fabio Estevam
2020-10-14 13:26 ` Miquel Raynal
2020-10-15 19:24 ` Fabio Estevam
2020-10-16 3:04 ` Han Xu
2020-10-16 6:39 ` Sascha Hauer
2020-10-16 7:53 ` Miquel Raynal
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=20201013193652.0c535c7c@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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.