mail archive of the barebox mailing list
 help / color / mirror / Atom feed
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 2019.07 ubiformat
Date: Thu, 26 Sep 2019 08:41:16 +0200	[thread overview]
Message-ID: <20190926064116.aix5mx2fwtbqyrzc@pengutronix.de> (raw)
In-Reply-To: <MN2PR16MB3117C56576A8FB7A258431B691870@MN2PR16MB3117.namprd16.prod.outlook.com>

Hi Renaud,

On Wed, Sep 25, 2019 at 05:44:16PM +0000, Barbier, Renaud wrote:
> We recently jumped from barebox 2016.07 to 2019.07. 
> Everything went well till the NAND got ubiformated.
> 
> Using the version from2016.07, the NOR boot partition can be formatted (FIT image) and NAND (file system) and the system boots.
> When using the barebox 2019-07, both storage can be formatted but when booting (Linux 4.16 or 5.2) I get:

There is no driver for this NAND controller upstream, I assume you have
it in your tree, right? Can barebox itself read what it has written,
i.e. ubiattach / mount it?

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 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

  reply	other threads:[~2019-09-26  6:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 17:44 Barbier, Renaud
2019-09-26  6:41 ` Sascha Hauer [this message]
2019-09-26 14:15   ` Barbier, Renaud
2019-09-27  6:44     ` Sascha Hauer
2019-09-27  8:43       ` Barbier, Renaud
2019-10-18 14:36         ` Barbier, Renaud
2019-10-18 15:09           ` Barbier, Renaud
2019-10-21  7:52             ` Sascha Hauer

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=20190926064116.aix5mx2fwtbqyrzc@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