--- In "Charles" <> wrote:
>
>
> Hi --
>
> --- In "j.chitte" <j.chitte@> wrote:
> >
> > Hi,
> >
> > I'm having some problems accessing mtd devices with 2.6.32.11 with
> > Matthieu's patches .
> >
> > All works well booting nfs but if I try to mount or erase the mtd devices ,
> > no go.
> >
> > # ls /dev/mtd* -ail
> >
> > 138 crw-rw---- 1 root root 90, 0 Jun 2 13:50 /dev/mtd0
> >
> > 139 crw-rw---- 1 root root 90, 1 Jun 2 13:50
> > /dev/mtd0ro
> > 140 crw-rw---- 1 root root 90, 2 Jun 2 13:50 /dev/mtd1
> >
> > 141 crw-rw---- 1 root root 90, 3 Jun 2 13:50
> > /dev/mtd1ro
> > 142 crw-rw---- 1 root root 90, 4 Jun 2 13:50 /dev/mtd2
> >
> > 143 crw-rw---- 1 root root 90, 5 Jun 2 13:50
> > /dev/mtd2ro
> > 118 brw-rw---- 1 root root 31, 0 Jun 2 13:50
> > /dev/mtdblock0
> > 119 brw-rw---- 1 root root 31, 1 Jun 2 13:50
> > /dev/mtdblock1
> > 120 brw-rw---- 1 root root 31, 2 Jun 2 13:50
> > /dev/mtdblock2
> >
> >
> > # flash_eraseall /dev/mtd1
> > flash_eraseall: can't open '/dev/mtd1': Permission denied
> >
> > Try to mount mtdblock1 spews lots of badness about bad erase blocks.
> >
> >
> > From dmesg:
> >
> > Searching for NAND flash...
> >
> > NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V
> > 8-bit)
> > Scanning device for bad blocks
> >
> > Bad eraseblock 0 at 0x000000000000
> >
> > cmdlinepart partition parsing not available
> >
> > Using static partition definition
> >
> > Creating 3 MTD partitions on "ts7250-nand":
> >
> > 0x000000000000-0x000000004000 : "TS-BOOTROM"
> >
> > mtd: partition "TS-BOOTROM" doesn't end on an erase block -- force
> > read-only
> > 0x000000004000-0x000007d04000 : "Linux"
> >
> > mtd: partition "Linux" doesn't start on an erase block boundary -- force
> > read-only
> > 0x000007d04000-0x000008000000 : "RedBoot"
> >
> > mtd: partition "RedBoot" doesn't start on an erase block boundary -- force
> > read-only
> >
> >
> > Some digging indicates this seems to be due to incorrect page size , 2k on
> > TS7250, but this is coming up at redboot so presumably nothing to do with
> > yaffs but mtd.
>
> Matt used to have a patch for drivers/ntd/nand/ts7250.c that would change
> these hard-coded partition locations. In the patchset
> linux-2.6.29.1-ts7200-matt-4.tgz I'm looking at, it is patch
> 0023-ts7250_nand.patch. Is that not included any more?
>
> ISTR a way of detecting these locations dynamically was added, but I could be
> wrong. Your kernel is falling back to the hard-coded locations; maybe try
> applying the patch by hand and see how that goes. Or try to turn on dynamic
> redboot partition parsing.
>
> You can also double-check by booting a 2.4 TS image, and looking at the
> partition boundary locations printed during boot. They should match what you
> see in the patch.
>
> regards, ............ Charlie
>
> >
> > I see nothing the mtd sections that relates this other than the single
> > option to add specific support for ts boards.
> >
> > Is this option not aware of different page size or am I missing a trick?
> >
> > TIA.
> >
>
Thanks Charlie,
I've just come accross a post that I sent about a month ago that went
unanswered. It confirms that this patch got dropped.
>>
Mathieu's notes say:
Gets rid of 5 patch files!
NAND specific driver (ts7250.c) is getting obsolete with generic NAND platform
driver.
My 2.6.29 kernel with this patches works fine. But my latest build is having
problems...
>>
I think the only reason I went for a more recent kernel was updating
crosstools-ng did not support 2.6.29. I'll see if I can retrofit the older
kernel that worked well or apply the patch.
I'm a bit surprised if Matthieu's retired this patch prematurely , maybe I'm
missing something.
Thanks for your help.
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|