[DOC2000] invalid size detected

[DOC2000] invalid size detected

[David Girault]

Hi all,

I am trying to access a 8MB DOC2000 using kernel 2.4.20 and MTD lasted CVS
version (using patchin.sh).

The current CVS version detect a bad size for my DOC device when I load
modules using :
  /sbin/modprobe -a doc2000 nftl mtdchar
  /sbin/modprobe -a docprobe

The previous version I build (2.4.18) detect the correct size but lack for
UnitSizeFactor!=1 support.

I think the problem is in the NAND_IDS.C chip identification but I am not
sure.
As I can see, there is a name conflict beetween nand_ids.h and nand_ids.c.

What de you think of this problems/bug?

Thank.
David.


-------------------------

LOG for 2.4.20+MTD CVS:

  NFTL driver: nftlcore.c $Revision: 1.87 $, nftlmount.c $Revision: 1.31 $
  Using configured DiskOnChip probe address 0xdc000
  DiskOnChip 2000 found at address 0xDC000
  Flash chip found: Manufacturer ID: EC, Chip ID: E6 (NAND 2MB 5V)
  1 flash chips found. Total DiskOnChip size: 2 MiB
  NFTL: UnitSizeFactor 0x00 detected. This violates the spec but we think we
know
  what it means...
  NFTL Media Header sanity check failed:
  numvunits (1984) > nb_blocks (512) - nb_boot_blocks(8) - 2
  Could not find valid boot record
  Could not mount NFTL device

cat /proc/mtd:

  dev:    size   erasesize  name
  mtd0: 00200000 00001000 "DiskOnChip 2000"

-------------------------

LOG for 2.4.18:

  NFTL driver: nftlcore.c $Revision: 1.82 $, nftlmount.c $Revision: 1.25 $
  Using configured DiskOnChip probe address 0xdc000
  DiskOnChip 2000 found at address 0xDC000
  Flash chip found: Manufacturer ID: EC, Chip ID: E6 (Samsung KM29U64000)
  1 flash chips found. Total DiskOnChip size: 8 MiB
  Sorry, we don't support UnitSizeFactor of != 1 yet.
  Could not find valid boot record
  Could not mount NFTL device

cat /proc/mtd:
  dev:    size   erasesize  name
  mtd0: 00800000 00002000 "DiskOnChip 2000"

Re: [DOC2000] invalid size detected

[Thomas Gleixner]

On Tuesday 10 December 2002 15:33, David Girault wrote:
> The previous version I build (2.4.18) detect the correct size but lack for
> UnitSizeFactor!=1 support.
>
> I think the problem is in the NAND_IDS.C chip identification but I am not
> sure.
> As I can see, there is a name conflict beetween nand_ids.h and nand_ids.c.
nand_ids.h is not longer in the CVS. I moved the ID's into nand_ids.c and 
splitted the tables.
 
> What de you think of this problems/bug?
I should not hack, when I'm tired :)

Fixed in CVS. Could you please try and bang me, if it's not working as 
exspected.

-- 
Thomas
____________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

Re: [DOC2000] invalid size detected

[David Girault]

Hi,

> I have a disk-on-chip with 16MB (kernel 2.4.20), and in /proc/mtd I see
> mtd0: 01000000 00004000 "DiskOnChip 2000"
>
> thats not 16meg, do I have the same problem as you ? (as my flash is
rather
> mailfunctioning)

This is 16meg in hexadecimal. So it is Ok.
I think you have another problem.

David

Re: [DOC2000] invalid size detected

[David Girault]

> > The previous version I build (2.4.18) detect the correct size but lack
for
> > UnitSizeFactor!=1 support.
> >
> > I think the problem is in the NAND_IDS.C chip identification but I am
not
> > sure.
> > As I can see, there is a name conflict beetween nand_ids.h and
nand_ids.c.
> nand_ids.h is not longer in the CVS. I moved the ID's into nand_ids.c and
> splitted the tables.

nand_ids.h still in include dir of kernel source (2.4.20).
I think the patchin.sh script should erase it before making links.
But your change works even if this file is in the include path.

>
> > What de you think of this problems/bug?
> I should not hack, when I'm tired :)
>
> Fixed in CVS. Could you please try and bang me, if it's not working as
> exspected.

It's now working. I can acces the DOS partition.


Many thanks
--
David