From: Ciro Cattuto <ciro@prosa.it>
To: mtd@infradead.org
Subject: Re: nftl_format and 2 Mb DOC
Date: Sat, 26 Aug 2000 09:15:47 +0200 [thread overview]
Message-ID: <20000826091547.A16896@localhost> (raw)
In-Reply-To: <20000825194211.A14265@localhost>; from ciro@prosa.it on Fri, Aug 25, 2000 at 07:42:11PM +0200
On Fri, Aug 25, 2000 at 07:42:11PM +0200, Ciro Cattuto wrote:
> ...now, 2 Mb DOC have 4k erase size, and I'd like to add support for this.
> Is there something I should be aware of before I start hacking to make
> nftl_format happy, instead than confused? ;)
The code in nftl_format looks pretty independent of the erase zone size,
so I simply removed the check against 0x2000. It seems to work fine,
except for an error while writing OOB data, which I'm not sure is related
to nftl_format itself.
Ciro
--
Ciro Cattuto, Open Source Developer, Linuxcare Italia SpA
Tel. +39.338.3002140 Fax +39.049.8036484
ciro@linuxcare.com http://www.linuxcare.com/
ciro@prosa.it http://www.prosa.it/
Linuxcare. Support for the revolution.
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
prev parent reply other threads:[~2000-08-26 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-25 17:42 nftl_format and 2 Mb DOC Ciro Cattuto
2000-08-26 7:15 ` Ciro Cattuto [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=20000826091547.A16896@localhost \
--to=ciro@prosa.it \
--cc=mtd@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