From: Dan Brown <dan_brown@ieee.org>
To: andrew box <andr3wbox@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: differences between NFTL and INFTL
Date: Fri, 04 Mar 2005 08:34:17 -0500 [thread overview]
Message-ID: <422863D9.6010109@ieee.org> (raw)
In-Reply-To: <66f646fd05030323395ed3a52c@mail.gmail.com>
andrew box wrote:
> I have a diskonchip2000dip(NFTL) with jffs2,and I want to use it as a
> boot device,while docboot just support INFTL now...that is the reason
> why I want to know the difference between them.
The DOC2000 parts that use INFTL have a different controller chip
(derived from the one used in the DOC Millennium, rather than the one in
the original NFTL-based DOC2000). The register locations, command
sequences, etc. are all slightly different.
Also, the boot loader in the NFTL-based parts' ROM does things a bit
differently from the way it works on the INFTL parts.
Having said all that, the differences are well understood and would only
affect small portions of docboot. The task of porting docboot to the
NFTL-based parts should not be large.
All we need is a volunteer :)
-Dan
next prev parent reply other threads:[~2005-03-04 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 7:39 differences between NFTL and INFTL andrew box
2005-03-04 13:34 ` Dan Brown [this message]
2005-03-05 11:27 ` andrew box
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=422863D9.6010109@ieee.org \
--to=dan_brown@ieee.org \
--cc=andr3wbox@gmail.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