From: Ruediger Haertel <hae@port.de>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: MTD/ DoC Millenium Plus - Failure in flash detection
Date: Fri, 8 Jul 2005 10:48:17 +0200 [thread overview]
Message-ID: <200507081048.18115.hae@port.de> (raw)
In-Reply-To: <200507071704.19393.hae@port.de>
> > >
> > > 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.
>
> Now I used the nanddump from mtd-cvs 2005-03-03. The same result. It
> reads oobsize and oobblock as 0.
>
> I printed the values of the mtd structure during probing and they
> are: oob size: 16, oob block: 512
>
> Seems ok. So I guess my device file is not correct. I am
> using /dev/mtd5,c,90,9.
>
Stupid me. Of course it was the wrong device file. MTD Devices have an
even minor number (mtd->index*2). The odd minor (mtd->index* 2+1)
number is used for readonly device files. Now I use the device
file /dev/mtd5,c,90,10.
Now I get output from nanddump. But I cannot see the file contents that
I wrote to the DoC.
testfile: "0123456789ABCDEF"
/> nandwrite -p /dev/mtd5 /mnt/testfile
MTD_open
MTD_ioctl
MTD_ioctl
Writing data to block 0
MTD_ioctl
Bad block at 0, 1 block(s) from 0 willM be skipped
Writing dataT to block 4000
D_ioctl
MTD_write
MTD_close
Seems to have worked. However nanddump (I dumped the complete 16 MB)
does not show the file contents on the DoC.
Do I have to format the DoC or do any other preparation? I thought that
was only necessary with the "old" driver.
This is also my next step. Preparing for a filesystem. I think I have to
format it with the ntfl_format tool and then mkfs.jff2. Right?
--
Ruediger Haertel
next prev parent reply other threads:[~2005-07-08 8:48 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
2005-07-07 14:00 ` Thomas Gleixner
2005-07-07 15:04 ` Ruediger Haertel
2005-07-08 8:48 ` Ruediger Haertel [this message]
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=200507081048.18115.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox