From: Vipin Malik <vmalik@danielind.com>
To: Amit D Chaudhary <amitc@brocade.com>
Cc: Vipin Malik <Vipin.Malik@daniel.com>,
"'mtd@infradead.org'" <mtd@infradead.org>
Subject: Re: Unable to mount compressed root f/s because init_mtd() does not r egister block device!
Date: Thu, 22 Feb 2001 14:01:09 -0600 [thread overview]
Message-ID: <3A957005.3400694E@danielind.com> (raw)
In-Reply-To: 3A956884.2050504@brocade.com
Bacause, the ram disk driver needs a registered block device to
decompress from. This code already exists in the linux kernel (see
drivers/block/rd.c)
(to uncompress a compressed root file system image). I don't want to
write it again.
Also, as far as reading goes, there is no real difference between the
mtd0 device and the block device (i.e. reading from
mtd0 does not get you anything extra).
Vipin
Amit D Chaudhary wrote:
> Hi,
>
> A question here, why not uncompress from the raw mtd device(that is
> /dev/mtd0, /dev/mtd1, etc) instead?
>
> Thanks
> Amit
>
> Vipin Malik wrote:
>
> > In 2.2.18 patched with the 2.2.18 patch, I'm trying to boot
> > a kernel from raw (CFI) flash and decompress an ext2 root
> > f/s image (from /dev/mtdblock0) into ramdisk and mount it as root.
> >
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-02-22 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 4:19 Unable to mount compressed root f/s because init_mtd() does not r egister block device! Vipin Malik
[not found] ` <3A956884.2050504@brocade.com>
2001-02-22 20:01 ` Vipin Malik [this message]
2001-02-23 8:22 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-02-22 21:55 Unable to mount compressed root f/s because init_mtd() does n ot " David Woodhouse
2001-02-22 22:41 ` Unable to mount compressed root f/s because init_mtd() does not " Vipin Malik
2001-02-23 8:24 ` David Woodhouse
2001-02-23 18:02 ` Vipin Malik
2001-02-23 17:37 ` 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=3A957005.3400694E@danielind.com \
--to=vmalik@danielind.com \
--cc=Vipin.Malik@daniel.com \
--cc=amitc@brocade.com \
--cc=mtd@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