Thanks for your responses, but a few questions still remains.
1- I should keep partitions "u-boot", "u-boot env" and "devdata" from stock
firmware, correct?
2- What the second parameter in reg means? Like 0x10000 on the example
below:
partition@30000 {
label = "u-boot-env";
reg = <0x30000 0x8000>;
read-only;
};
3- Would guys help me create proper partitions on my dts file? If some info
is missing, please tell me.
----- Original Message -----
From: "Florian Fainelli" <[email protected]>
To: "OpenWrt Development List" <[email protected]>
Sent: Monday, June 24, 2013 8:36 AM
Subject: [Spam] Re: [OpenWrt-Devel] Help with DTS file
2013/6/24 [email protected] <[email protected]>:
On Mon, Jun 24, 2013 at 4:53 AM, Florian Fainelli <[email protected]>
wrote:
2013/6/24 [email protected] <[email protected]>:
On Sun, Jun 23, 2013 at 5:50 PM, Flávio Silveira <[email protected]>
wrote:
Good evening,
I'm trying to create a dts file for my router which is not supported
yet
and I'm stuck on the definition of partitions.
Do I have to follow the same as stock firmware?
Router's serial log with stock firmware shows this:
Creating 8 MTD partitions on "raspi":
0x000000150060-0x0000003cc060 : "rootfs"
0x000000050000-0x0000003e0000 : "upgrade"
0x000000040000-0x000000050000 : "devconf"
0x000000030000-0x000000040000 : "devdata"
0x0000003e0000-0x000000400000 : "langpack"
0x000000000000-0x000000400000 : "flash"
0x000000000000-0x000000030000 : "u-boot"
0x000000030000-0x000000038000 : "boot env"
Partitions should not overlap. This partition table doesn't seem to be
valid.
Parititions can overlap, even with DT, but you just need to make sure
that node addresses are unique, such that if you want to make
overlapping partitions of this kind:
Why would you want overlapping partitions?
You may have a combined kernel+rootfs partition and a corresponding
binary image which you flash directly at the right address (say
kernel+rootfs) withouth having to do any split between the kernel and
rootfs binaries. There might be plenty of other valid uses cases.
--
Florian
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
