From: David Woodhouse <dwmw2@infradead.org>
To: "Rogelio M. Serrano Jr." <rogelio@evoserve.com>
Cc: mtd@infradead.org
Subject: Re: mtd devices & jffs
Date: Wed, 12 Jul 2000 09:20:50 +0100 [thread overview]
Message-ID: <21762.963390050@cygnus.co.uk> (raw)
In-Reply-To: <396BC59F.47F1B14F@evoserve.com>
rogelio@evoserve.com said:
> The same happens to me and im using a DOC2000. The second time i mount
> jffs fails to build the tree.
Doc2000 doesn't currently support writes which aren't 512 bytes long, which
isn't particularly useful for JFFS. S'fairly trivial to fix. Just that
nobody's done it yet. You don't need to know anything about the DiskOnChip
to do it - just read the datasheet for the flash chips it's using.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-07-12 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-10 22:19 mtd devices & jffs Juan Gonzo
2000-07-11 6:37 ` Rogelio M. Serrano Jr.
2000-07-11 7:30 ` David Woodhouse
2000-07-12 1:10 ` Rogelio M. Serrano Jr.
2000-07-12 8:20 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-11 21:23 Juan Gonzo
2000-07-12 8:19 ` David Woodhouse
2000-07-12 9:35 ` 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=21762.963390050@cygnus.co.uk \
--to=dwmw2@infradead.org \
--cc=mtd@infradead.org \
--cc=rogelio@evoserve.com \
/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