From: Simon Haynes <simon@baydel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: SmartMedia FAT
Date: Thu, 30 Oct 2003 14:26:30 +0000 [thread overview]
Message-ID: <EDC19A8677F@baydel.com> (raw)
In-Reply-To: <1067424903.15551.1537.camel@hades.cambridge.redhat.com>
I have been looking at the OOB data format for SSFDC and it seems I will have
to create and process my own OOB data as I can not see how the NAND/MTD layer
will work with this.
When we started this project there seemed to be a fixed NAND OOB format. Now
the NAND OOB format is selectable. I have noticed in a couple of kernel
distributions that the JFFS2 code does not seem to be aware of this and just
calls pain mtd->read. I guess this would mean no ecc for JFFS2 on NAND unless
it was done automatically by the hardware. This was the case for latest
stable kernel, 2.4.22 downloaded from kernel.org today.
Is this really the case ?
Cheers
Simon.
On Wednesday 29 Oct 2003 10:55 am, David Woodhouse wrote:
> On Wed, 2003-10-29 at 10:21 +0000, simon@baydel.com wrote:
> > Thanks too all for your help. I have started to write my own block
> > driver using the FTL code as a guide. It seems fairly simple and
> > should not take too long.
>
> Send me a SSH key and I'll give you an account so you can put it in CVS.
> Commit early and often and I'll try to heckle helpfully... :)
next prev parent reply other threads:[~2003-10-30 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 15:45 SmartMedia FAT simon
2003-10-27 20:34 ` Charles Manning
2003-10-28 11:11 ` David Woodhouse
2003-10-28 23:33 ` Charles Manning
2003-10-29 0:48 ` David Woodhouse
2003-10-29 9:40 ` Jasmine Strong
2003-10-29 20:33 ` Charles Manning
2003-10-29 10:21 ` simon
2003-10-29 10:55 ` David Woodhouse
2003-10-30 14:26 ` Simon Haynes [this message]
2003-10-30 15:03 ` 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=EDC19A8677F@baydel.com \
--to=simon@baydel.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