All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ruediger Haertel <hae@port.de>
To: linux-mtd@lists.infradead.org
Cc: tglx@linutronix.de
Subject: Re: MTD/ DoC Millenium Plus - Failure in flash detection
Date: Thu, 7 Jul 2005 15:32:17 +0200	[thread overview]
Message-ID: <200507071532.17991.hae@port.de> (raw)
In-Reply-To: <1120742513.26713.106.camel@tglx.tec.linutronix.de>

Am Donnerstag, 7. Juli 2005 15:21 schrieb Thomas Gleixner:
> On Thu, 2005-07-07 at 15:05 +0200, Ruediger Haertel wrote:
> > For the NAND DiskOnChip driver I had to apply the patch mentioned
> > here:
> > http://lists.infradead.org/pipermail/linux-mtd/2004-October/010640.
> >html
> >
> >
> > What irritates me is the output:
> > DiskOnChip BNAND Media Header not found.
> >
> > Why is that ?
>
> Obviously the header is not at the expected place.
>
> > />nanddump /dev/mtd5 /var/xxx 0 128
> > MTD_open
> > MTD_ioctl
> > Unknown flash (not normalM NAND)
>
> Is this nanddump from latest MTD-CVS ?

No. I use the one of the uClinux-dist-20041215. I'll give the one from 
mtd-cvs a try. Should I use realy the latest snapshot or the one I am 
using from date 2005.03.03.



So from your point the other messages from my output are ok ?

nand_read_ecc: Failed ECC read, page 0x00000020 on chip 0
ECC error scanning DOC at 0x4000
nand_read_ecc: Failed ECC read, page 0x00000040 on chip 0
ECC error scanning DOC at 0x8000
nand_read_ecc: Failed ECC read, page 0x00000060 on chip 0
ECC error scanning DOC at 0xc000
doc200x_correct_data corrected 2 errors
nand_read_ecc: Failed ECC read, page 0x00000080 on chip 0
ECC error scanning DOC at 0x10000


-- 

Ruediger Haertel

  reply	other threads:[~2005-07-07 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06 15:45 MTD/ DoC Millenium Plus - Failure in flash detection Ruediger Haertel
2005-07-07 13:05 ` Ruediger Haertel
2005-07-07 13:21   ` Thomas Gleixner
2005-07-07 13:32     ` Ruediger Haertel [this message]
2005-07-07 14:00       ` Thomas Gleixner
2005-07-07 15:04       ` Ruediger Haertel
2005-07-08  8:48         ` Ruediger Haertel
2005-07-08  9:21           ` Ruediger Haertel
2005-07-11  8:04           ` Ruediger Haertel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200507071532.17991.hae@port.de \
    --to=hae@port.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.