On Fri, 2014-02-07 at 23:33 +0100, Marco Antonio Mauro wrote:
> On Fri, Feb 7, 2014 at 12:38 PM, Marco Antonio Mauro
> wrote:
> > I think I found out the cause. The partition rootfs data gets created
> > after the squashfs one at 0x73 in my case, but there there's the
> > sercomm signature an
On Fri, Feb 7, 2014 at 12:38 PM, Marco Antonio Mauro wrote:
> I think I found out the cause. The partition rootfs data gets created
> after the squashfs one at 0x73 in my case, but there there's the
> sercomm signature and checksum needed for the bootloader there, and
> the deadc0de jffs2 magi
I think I found out the cause. The partition rootfs data gets created
after the squashfs one at 0x73 in my case, but there there's the
sercomm signature and checksum needed for the bootloader there, and
the deadc0de jffs2 magic is instead at 0x74, and that's where the
partition should start
Hi,
I had a similar problem on the BT Home Hub 2B, which also
has nand flash. The problem as you say seems to be that
mount_root assume that the deadc0de will be at the start
of the block where it would be for nor flash. I expect others
will have a better idea of the right way to solve this (perha
Hi,
the router I'm working on at the moment, the DGN3500 lantiq platform,
has a strange issue: it won't create or save the configuration. I see
this in the logs:
[0.00] Linux version 3.10.26 (marcus905@experiment) (gcc
version 4.6.4 (OpenWrt/Linaro GCC 4.6-2013.05 r39286) ) #39 Thu Feb 6
