From: Thorsten Haas <haas@deutaeit.de>
To: Ralph Siemsen <ralphs@netwinder.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: CFI physmap - how to create partitions
Date: Fri, 20 May 2005 15:20:57 +0200 [thread overview]
Message-ID: <1116595257.2718.34.camel@shrek> (raw)
In-Reply-To: <428DDF13.8030503@netwinder.org>
Am Freitag, den 20.05.2005, 08:58 -0400 schrieb Ralph Siemsen:
> Thorsten Haas wrote:
>
> > Yes, they are the same. Yes, they are consecutive in memory. Yes, I
> > tried that. Yes, it's now less undocumented, because my diff contains
> > this information :)
>
> Excellent.
>
> > Well, actually, when using physmap.c I am able to create partitions, but
> > there is still some trouble when using the mtd partitions: erasing and
> > mounting fails.
> >
> > Does someone have an idea, what I am doing wrong?
> >
> > # flash_erase /dev/mtd0
> > File open error
>
> That's a bit worrysome... Not sure if it checks for this, but do you
> have this partition mounted at the time?
Nope, not mounted.
> Also check in /proc/devices that major 90 is in fact registered.
It is registered. Device nodes are also present.
> > # flash_erase /dev/mtd4 0x0 0x40
> > Erase Total 64 Units
> > Performing Flash Erase of length 131072 at offset 0x160000
> > MTD Erase failure: Invalid argument
>
> Hmm, I always use "flash_eraseall" command myself, so I don't have to
> worry about the block numbers and such. But I doubt this makes any
> difference, your problem seems to lie elsewhere.
>
> -R
prev parent reply other threads:[~2005-05-20 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 8:05 CFI physmap - how to create partitions Thorsten Haas
2005-05-18 22:35 ` Ralph Siemsen
2005-05-19 8:06 ` Thorsten Haas
2005-05-19 11:54 ` Ralph Siemsen
2005-05-20 7:26 ` Thorsten Haas
2005-05-20 12:58 ` Ralph Siemsen
2005-05-20 13:20 ` Thorsten Haas [this message]
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=1116595257.2718.34.camel@shrek \
--to=haas@deutaeit.de \
--cc=linux-mtd@lists.infradead.org \
--cc=ralphs@netwinder.org \
/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.