From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Stefan Riedmueller <s.riedmueller@phytec.de>
Subject: [PATCH RFC] imx6ul-phytec-phycore-som: don't use fsl, no-blockmark-swap for the NAND
Date: Tue, 8 Jan 2019 11:24:12 +0100 [thread overview]
Message-ID: <20190108102412.10553-1-u.kleine-koenig@pengutronix.de> (raw)
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?
Best regards
Uwe
arch/arm/dts/imx6ul-phytec-phycore-som.dtsi | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/dts/imx6ul-phytec-phycore-som.dtsi b/arch/arm/dts/imx6ul-phytec-phycore-som.dtsi
index d829fdd6fb29..398546d7b92e 100644
--- a/arch/arm/dts/imx6ul-phytec-phycore-som.dtsi
+++ b/arch/arm/dts/imx6ul-phytec-phycore-som.dtsi
@@ -49,7 +49,6 @@
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_gpmi_nand>;
nand-on-flash-bbt;
- fsl,no-blockmark-swap;
status = "disabled";
#address-cells = <1>;
--
2.20.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2019-01-08 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 10:24 Uwe Kleine-König [this message]
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 ` [PATCH RFC] imx6ul-phytec-phycore-som: don't use fsl, no-blockmark-swap " 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=20190108102412.10553-1-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.riedmueller@phytec.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