From: Tom McMillan <tsm@airfiber.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Eraseblock size in jffs2 ?
Date: Wed, 10 Oct 2001 09:44:13 -0700 [thread overview]
Message-ID: <3BC47ADD.504E81C3@airfiber.com> (raw)
In-Reply-To: 22822.1002731498@redhat.com
David Woodhouse wrote:
>
> Unfortunately, JFFS2 doesn't yet work on the DiskOnChip, because it uses
> NAND flash. JFFS v1 should probably work, or you can fix up JFFS2 to work
> too.
>
Where, exactly? Or at least, a starting point. I've just started
looking into using JFFS2 with my DOC2000s.
_____________________________________________________________________
Tom McMillan AirFiber
tsm@airfiber.com 16510 Via Esprillo
PH: (858) 676-7301 San Diego, CA 92127
next prev parent reply other threads:[~2001-10-10 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 16:31 Eraseblock size in jffs2 ? martin.kula
2001-10-10 16:31 ` David Woodhouse
2001-10-10 16:44 ` Tom McMillan [this message]
2001-10-10 16:47 ` David Woodhouse
2001-10-10 17:16 ` martin.kula
2001-10-10 17:39 ` David Woodhouse
2001-10-10 17:58 ` martin.kula
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=3BC47ADD.504E81C3@airfiber.com \
--to=tsm@airfiber.com \
--cc=dwmw2@infradead.org \
--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