From: David Woodhouse <dwmw2@infradead.org>
To: Eric Nelson <eric_n2@verifone.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Alternate to DOC??
Date: Fri, 15 Feb 2002 06:49:56 +0000 [thread overview]
Message-ID: <17310.1013755796@redhat.com> (raw)
In-Reply-To: <614CC7C21856D1118DA30060B06B487302ACC8D0@SMF-NT-MAIL1>
eric_n2@verifone.com said:
> We would very much like to use JFFS2 on a project. However, most
> boards have either CF or DOC. My understanding of JFFS2 on DOC is
> that you disable the controller on the DOC, and just use the flash.
No, you can use the controller. All it does is ECC. The NFTL stuff was all
done in software anyway.
> Now, wouldn't it be a good idea for someone to build a device w/ same
> footprint as DOC, but w/ just raw flash? Maybe we could do this.
> Would this impinge on some patent by M-Systems? It would make it a
> lot easier for us to use JFFS2 if we could do this.
The socket and pin layout are standard, I believe. There's no problem with
making an alternative device to fit.
--
dwmw2
next prev parent reply other threads:[~2002-02-15 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 18:50 Alternate to DOC?? Eric Nelson
2002-02-15 6:49 ` David Woodhouse [this message]
2002-02-15 9:11 ` Thomas Gleixner
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=17310.1013755796@redhat.com \
--to=dwmw2@infradead.org \
--cc=eric_n2@verifone.com \
--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