From: pla <pla@tmok.com>
To: linux-mtd@lists.infradead.org
Subject: Re: DOC2000 erase size of 16k?
Date: Mon, 13 Aug 2001 15:25:47 -0400 (EDT) [thread overview]
Message-ID: <200108131925.PAA19680@stone.tmok.com> (raw)
> Er, that code is older than the 20010807 snapshot you said you were using.
> I meant the latest code from my CVS. I'm slightly concerned that the older
> code works when the newer code doesn't - it's supposed to work the other
> way round. Can you check the latest code and make sure it works there too?
Hmm, yes, the 20010812 snapshot works correctly. I just diff'd the two
snapshots, and would have to say that the problems I experienced did not
result from anything in the MTD code, so don't trouble yourself with
what went wrong. I must have accidentally whacked something without
noticing. My apologies for wasting your time.
> It doesn't work perfectly yet, although it shouldn't take much to fix it.
> To make it fit, you have to use nftl_format to make the NFTL start further
> in to the device.
Ah! Now I see how this all fits together. Many thanks, and I will
certainly write up my experiences for the HowTo. Incidentally, for
anyone else trying this, it would serve them well to back up the
bad blocks section of their DOC before doing *anything*. I seem
to have killed my DOC by overwriting it, without a backup (fortunately,
I can just get another from work, but not everyone has that
luxury).
- Ben
next reply other threads:[~2001-08-13 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 19:25 pla [this message]
2001-08-13 23:56 ` DOC2000 erase size of 16k? David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-08-14 1:40 pla
2001-08-13 1:29 pla
2001-08-13 7:37 ` David Woodhouse
2001-08-12 23:33 pla
2001-08-12 23:46 ` David Woodhouse
2001-08-13 14:40 ` Vipin Malik
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=200108131925.PAA19680@stone.tmok.com \
--to=pla@tmok.com \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox