mtd_debug usage

[Duke]

On 11/22/06, Artem Bityutskiy <dedekind at infradead.org> wrote:
> On Wed, 2006-11-22 at 15:46 +0100, Ricard Wanderlof wrote:
> > The minor numbers for /dev/mtdX are wrong. /dev/mtd0 should have a minor
> > no. of 0, /dev/mtd1 should have 2, /dev/mtd2 should have 4 etc. The
> > odd-numbered minor numbers are intended for read-only devices.
>
> There is MKDEVS scripts an mtd-utils which can create these.
>

Thanks all,
I got it right now and it does show the correct info.

However, What does the following mean?

#mtd_debug write /dev/mtd2 0x0 0x600000 testfs_cramfs
file_to_flash: fread, size 0x600000, n 0x600000
fread(): Success

Does that mean it will write to mtd2 which starts at physical address
0x200000 (to 0x800000) or does it actually start at physical address
0x0?
 what does the n means?
I'm not writing to flash correctly so maybe I'm missing something.

Thanks.