From: "Pieter Grimmerink" <mailinglists@grimmerink.nl>
To: "Poul Lund Jørgensen" <plj@pragmaticconsult.com>
Cc: <linux-mtd@lists.infradead.org>
Subject: RE: jffs2 on DOC ?
Date: Tue, 21 May 2002 18:04:10 +0200 [thread overview]
Message-ID: <MPBBIIEFELAEABNCNHMMGENFDAAA.mailinglists@grimmerink.nl> (raw)
In-Reply-To: <005d01c200d6$a0f88c80$0201a8c0@PLJPC>
> -----Original Message-----
> From: linux-mtd-admin@lists.infradead.org
> [mailto:linux-mtd-admin@lists.infradead.org]On Behalf Of Poul Lund
> Jørgensen
> Sent: dinsdag 21 mei 2002 16:49
> To: linux-mtd@lists.infradead.org
> Subject: jffs2 on DOC ?
> Another solution would be to run jffs2 on the DOC. But the drivers that
> comes with the kernel I use (2.4.18) does not support this.
According to David Woodhouse, all that's left to do to make DOC support
JFFS2, is to make the write/read functions handle more than 512 bytes
of data.
I've quickly looked into this, but I'm not sure whether just adding a loop
within these functions would do, as I haven't found how bad sectors
are handled within the write/read functions yet.
I could imagine that the file offset always points to the actual location
in the DOC, so that we could have a write of lets say 4 bytes, and
a bad sector in the middle would then cause the file offset to be increased
with 516, but I'm not sure.
I'll eventually need JFFS2 on DOC, but it isn't currenly the first point on
my list,
so I'm secretly hoping someone will fix it before I need it ;-)
Regards,
Pieter
prev parent reply other threads:[~2002-05-21 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 14:48 jffs2 on DOC ? Poul Lund Jørgensen
2002-05-21 16:04 ` Pieter Grimmerink [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=MPBBIIEFELAEABNCNHMMGENFDAAA.mailinglists@grimmerink.nl \
--to=mailinglists@grimmerink.nl \
--cc=linux-mtd@lists.infradead.org \
--cc=plj@pragmaticconsult.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