From: David Woodhouse <dwmw2@infradead.org>
To: zeusj@firstlinux.net
Cc: all in MTD mailinglist <linux-mtd@lists.infradead.org>
Subject: Re: misc question about MTD
Date: Tue, 14 May 2002 08:40:19 +0100 [thread overview]
Message-ID: <23802.1021362019@redhat.com> (raw)
In-Reply-To: <20020514061754.D12882756@sitemail.everyone.net>
zeusj@firstlinux.net said:
> I think its just "assume" , If the Chip A and Chip B got QRY on the
> same location for data ,they will be still regarded as same chip, and
> that's the "FIXME" in your code means,isnt it:)
Yes.
> I think before mount the flash should be erased automatically ,but
> when I mount my flash (the mtd0 and mtdblock0 are all ok), I got the
> following message:
Strange. Is the flash completely erased? It should not be erased
automatically -- too many people attempt to mount the wrong flash
partition, and if you mount the partition that contains your bootloader you
will _not_ thank me for auto-erasing it.
I would strongly recommend you use JFFS2, not JFFS. I haven't looked at JFFS
code for ages now, and I don't think anyone else is doing so either.
> I analysed all the case ,but I think that's impossible to enter the
> "else" bracket theoretically Did I miss something or there is
> something special for the hardware?
Something special for the hardware. If you power cycle a chip while it's
erasing, you may find that some bits become undefined -- sometimes they'll
return a '1', other times a '0'.
--
dwmw2
next prev parent reply other threads:[~2002-05-14 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 6:17 misc question about MTD Jim Zeus
2002-05-14 7:40 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-15 18:34 Jim Zeus
2002-05-15 18:49 ` David Woodhouse
2002-05-10 6:43 Jim Zeus
2002-05-10 7:23 ` David Woodhouse
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=23802.1021362019@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=zeusj@firstlinux.net \
/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