From: Zeri Virgo <sillyzeri@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: boot from diskonchip with jffs2
Date: Sat, 26 Mar 2005 11:18:08 +0000 [thread overview]
Message-ID: <a2cb6db60503260318343be275@mail.gmail.com> (raw)
Hi,
I'm in search of an update to the issues discussed in this thread...
http://lists.infradead.org/pipermail/linux-mtd/2003-August/008327.html
I'm trying to determine the best method to boot and run from an old NAND
DiskOnChip (*not* TSOP). A while ago, I had success with the doc2000.c
driver...
/dev/mtd0 -> /dev/nftla -> /dev/nftla1 -> ext2 -> /(root of 64MB)
Is it feasile to use jffs2 for the root filesystem?
I understand the diskonchip.c code is ready for NFTL, reading the media
headers and mapping a separate "BDTL partition" for use.
So, should I...
1) not try to use jffs2 and just move over to a similar method as above
but with the diskonchip.c driver and root on the BDTL partition.
2) continue to use the deprecated doc2000.c driver and hack it to map
some "fake" partitions...
/dev/mtd0 -> /dev/nftla -> /dev/nftla1 -> ext2 -> /boot 2MB
/dev/mtd1 (/dev/mtdblock1) -> jffs2 /(root of 62MB)
3) use DOCBoot - right now I only need it for i586, but I may need it
for PowerPC and ARM/XScale eventually...and the README says NFTL DOCs
aren't yet supported.
4) use U-Boot http://www.denx.de/twiki/bin/view/DULG/DiskOnChip
5) use RedBoot - would need update on
http://lists.infradead.org/pipermail/linux-mtd/2005-January/011361.html
re. status of DiskOnChip support for the platforms I mentioned in 3
above? I'm going to look at the RedBoot code now...willing to have a go at
it if necessary.
6) use something else...?
- Zeri
next reply other threads:[~2005-03-26 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 11:18 Zeri Virgo [this message]
2005-03-26 15:03 ` boot from diskonchip with jffs2 Thomas Gleixner
2005-03-26 14:09 ` David Woodhouse
2005-03-26 14:54 ` Zeri Virgo
2005-03-26 14:59 ` 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=a2cb6db60503260318343be275@mail.gmail.com \
--to=sillyzeri@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