From: "Thomas Gleixner" <tglx@linutronix.de>
To: "Dan Brown" <dan_brown@ieee.org>, <linux-mtd@lists.infradead.org>
Cc: David Woodhouse <dwmw2@infradead.org>
Subject: Re: DOC support update
Date: Sat, 19 Jun 2004 02:07:42 +0200 [thread overview]
Message-ID: <200406190207.42609.tglx@linutronix.de> (raw)
In-Reply-To: <001501c4558c$4e42ce80$4402a8c0@tinker>
On Saturday 19 June 2004 01:30, Dan Brown wrote:
> The new NAND-subsystem-based DiskOnChip driver should now be fairly close
> to providing proper JFFS2 support, if it doesn't already. A tricky issue
> with the hardware ECC generator was discovered today, and hopefully solved.
Kudos to Dan for all his efforts.
> - Have a DOC Millenium or DOC2000 TSOP. Millenium+ is not supported (other
> folks are hard at work on this). DOC2000 original does not have BBT
> handling yet (coming soon!) and should not be used with JFFS2 yet.
Please join this effort as it will provide all the benefits of the generic
mtd/nand subsystem and help us avoid to have redundant and incompatible code.
At least the prospect to run JFFS2 or YAFFS on DoC should convince you of the
worthiness of this effort.
I'm positive that the Millenium+ efforts will show up with similar results
soon. The general problems of DoC support seem to be solved so it should be a
straight forward task despite of the device specific oddities to get it
running soon.
Please note that we plan to obsolete the DoC drivers in drivers/mtd/devices in
the long run and switch the DoC support completely over to mtd/nand. This
will affect the (I)NFTL layers too, as they will benefit from the nand
functionality too.
--
Thomas
_____________________________________________________________________
From slash dot org
"When customers are visiting, engineers are not allowed to wear ties.
That way the customer can tell who is the engineer and who is the
salesman (and therefore whom to believe.). Ties cut off blood flow
to the brain, making it easier for the salesmen to do their jobs."
_____________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
prev parent reply other threads:[~2004-06-19 0:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 23:30 DOC support update Dan Brown
2004-06-19 0:07 ` Thomas Gleixner [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=200406190207.42609.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=dan_brown@ieee.org \
--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