From: "Dan Brown" <dan_brown@ieee.org>
To: <linux-mtd@lists.infradead.org>
Subject: DOC support update
Date: Fri, 18 Jun 2004 19:30:56 -0400 [thread overview]
Message-ID: <001501c4558c$4e42ce80$4402a8c0@tinker> (raw)
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.
I say hopefully because I won't have a chance to really test it myself until
Monday. However, interested folks who don't have vital data on their DOC
devices are welcome to do so and provide feedback.
Brief HOWTO (better HOWTO coming soon!):
- 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.
- Load the new diskonchip module (there is now a kernel configuration option
for this under NAND devices). If your DOC device is not at window D000,
you'll have to edit the source or remap your chip. Proper probing coming
soon!
- A bunch of mtd devices should be created. mtd0 is the whole DOC. The
others are partitions created by M-Systems. A "BDK" partition is probably
the M-Sys BIOS driver. A "BDTL" partition is where your INFTL filesystem
used to be. I say used to be, because you're about to trash it.
- You can review the list of devices with 'cat /proc/mtd'
- Assuming your BDTL partition is mtd3:
flash_eraseall -j /dev/mtd3
mkfs.jffs2 -p -e 16384 -n -q -r <rootdir> -o <outputfile>
nandwrite /dev/mtd3 <outputfile from above>
mount -t jffs2 /dev/mtdblock3 <mountpoint>
- Cross your fingers.
Results, comments, etc appreciated.
-Dan Brown
next reply other threads:[~2004-06-18 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 23:30 Dan Brown [this message]
2004-06-19 0:07 ` DOC support update 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='001501c4558c$4e42ce80$4402a8c0@tinker' \
--to=dan_brown@ieee.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