public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Selwyn Tang <selwyn@hectrix.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Setting up compressed rootfs on DOC
Date: Mon, 17 Nov 2003 09:22:52 +0000	[thread overview]
Message-ID: <1069060971.4490.50.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <3F98EE07.20006@hectrix.com>

On Fri, 2003-10-24 at 17:16 +0800, Selwyn Tang wrote:
> Hi all,
> 
> I am used to running a DOC patched grub firmware on my DOC 2000 (16MB)
> with nftl, following the instructions of Karim's book. Since the space
> is running out, I am interested in using a compressed root fs.

There is no clever way to do this out of the box. If I needed this, I'd
do it as follows:

1. Fix the new NAND/DiskOnChip driver so it does hardware ECC and 
   correctly reads and enforces the Bad Block Table.

2. Use JFFS2 on your DiskOnChip.

3. Find/make a bootloader which can live in the DiskOnChip where
   Grub currently is and which groks JFFS2 so it can find and boot
   kernels from the file system. I'd probably use RedBoot for this,
   since the JFFS2 code is designed to work in eCos (on which
   RedBoot is based) and hence it shouldn't be hard to make
   JFFS2/NAND work in RedBoot.

You could skip step 3 if you put a tiny NFTL partition at the beginning
of the flash to hold the kernel, and just use JFFS2 on the rest.

-- 
dwmw2

      parent reply	other threads:[~2003-11-17  9:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-24  9:16 Setting up compressed rootfs on DOC Selwyn Tang
     [not found] ` <1068916696.17894.9.camel@localhost>
2003-11-17  2:21   ` Selwyn Tang
2003-11-17  9:22 ` David Woodhouse [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=1069060971.4490.50.camel@hades.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=selwyn@hectrix.com \
    /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