Hi!
> > I tried this one. Size 0xc0000 is reported as a "bootloader" during
> > boot.
> >
> > [Plus I get a warning from jffs2 that flashsize is not aligned to
> > erasesize. Then I get lot of messages that empty flash at XXX ends at
> > XXX.]
>
> What erase size did you end up using? Is 0xc0000 a multiple of it?
I ended up using ERASEINFO(0x10000,64), but I should probably be using
ERASEINFO(0x40000,16).
> > + subdev->mtd->unlock(subdev->mtd, 0xc0000, subdev->mtd->size);
>
> Probably unrelated to the actual problems, but shouldn't that be
> subdev->mtd->size - 0xc0000 at the end?
Fixed, thanks.
Pavel
--
Thanks, Sharp!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
