mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org,
	Stefan Riedmueller <s.riedmueller@phytec.de>
Subject: Re: [PATCH RFC] imx6ul-phytec-phycore-som: don't use fsl, no-blockmark-swap for the NAND
Date: Fri, 11 Jan 2019 12:03:03 +0100	[thread overview]
Message-ID: <20190111110302.gioxtjns6w5tfzqu@pengutronix.de> (raw)
In-Reply-To: <20190108102412.10553-1-u.kleine-koenig@pengutronix.de>

On Tue, Jan 08, 2019 at 11:24:12AM +0100, Uwe Kleine-König wrote:
> barebox doesn't honor that property which yields to inconsitencies
> between Linux and barebox after for example filling an UBI with a file
> system with barebox and then trying to mount that from Linux.
> 
> Note this is an interruptive change as it requires to rewrite the flash
> to make it working with Linux again.
> 
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Hello,
> 
> I wonder why Phytec chose to use this configuration. Was this just
> copied from another board?

Applied, thanks

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

      parent reply	other threads:[~2019-01-11 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 10:24 Uwe Kleine-König
2019-01-10 15:56 ` [PATCH RFC] imx6ul-phytec-phycore-som: don't use fsl,no-blockmark-swap " Stefan Riedmüller
2019-01-11 11:03 ` 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=20190111110302.gioxtjns6w5tfzqu@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.riedmueller@phytec.de \
    --cc=u.kleine-koenig@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox