mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Rostislav Lisovy <lisovy@gmail.com>
To: barebox@lists.infradead.org
Cc: Rostislav Lisovy <lisovy@gmail.com>, Pavel Pisa <pisa@cmp.felk.cvut.cz>
Subject: [RFC] ARM: dts: i.MX53: voipac: Provide NAND flash partition table
Date: Thu,  4 Sep 2014 17:33:19 +0200	[thread overview]
Message-ID: <1409844799-10338-1-git-send-email-lisovy@gmail.com> (raw)

Signed-off-by: Rostislav Lisovy <lisovy@gmail.com>
---
When compiled and loaded with the "imx-usb-loader" to RAM, the command
"saveenv" and "loadenv" do work properly (i.e. "loading environment
from /dev/nand0.environment.bb"). When I flash the barebox to the NAND
with the "barebox_update" command and reboot the device, the message
"environment load /dev/env0: No such file or directory" is provided
during boot. "saveenv" and "loadenv" do not know anything about
"/dev/nand0.environment.bb" anymore and try to access the "/dev/env0".
What am I doing wrong?


 arch/arm/dts/imx53-voipac-bsb.dts      |  1 +
 arch/arm/dts/imx53-voipac-dmm-668.dtsi | 33 +++++++++++++++++++++++++++++++++
 2 files changed, 34 insertions(+)
 create mode 100644 arch/arm/dts/imx53-voipac-dmm-668.dtsi

diff --git a/arch/arm/dts/imx53-voipac-bsb.dts b/arch/arm/dts/imx53-voipac-bsb.dts
index 54c8bcd..12ce592 100644
--- a/arch/arm/dts/imx53-voipac-bsb.dts
+++ b/arch/arm/dts/imx53-voipac-bsb.dts
@@ -10,4 +10,5 @@
  */
 
 #include <arm/imx53-voipac-bsb.dts>
+#include "imx53-voipac-dmm-668.dtsi"
 #include "imx53.dtsi"
diff --git a/arch/arm/dts/imx53-voipac-dmm-668.dtsi b/arch/arm/dts/imx53-voipac-dmm-668.dtsi
new file mode 100644
index 0000000..dfff1c2
--- /dev/null
+++ b/arch/arm/dts/imx53-voipac-dmm-668.dtsi
@@ -0,0 +1,33 @@
+/ {
+	chosen {
+		linux,stdout-path = &uart1;
+
+		environment@0 {
+			compatible = "barebox,environment";
+			device-path = &nfc, "partname:environment";
+		};
+	};
+};
+
+&nfc {
+	partition@0 {
+		label = "barebox";
+		reg = <0x0 0x80000>;
+	};
+
+	partition@1 {
+		label = "environment";
+		reg = <0x80000 0x80000>;
+	};
+
+	partition@2 {
+		label = "kernel";
+		reg = <0x100000 0x400000>;
+	};
+
+	partition@3 {
+		label = "rootfs";
+		reg = <0x500000 0x07B00000>;
+	};
+};
+
-- 
2.0.0.rc4


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2014-09-04 15:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 15:33 Rostislav Lisovy [this message]
2014-09-04 15:44 ` [PATCH] " Rostislav Lisovy
2014-09-05  5:42   ` 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=1409844799-10338-1-git-send-email-lisovy@gmail.com \
    --to=lisovy@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=pisa@cmp.felk.cvut.cz \
    /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