From: David Woodhouse <dwmw2@infradead.org>
To: Vipin Malik <vmalik@danielind.com>
Cc: Amit D Chaudhary <amitc@brocade.com>,
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: Fri, 23 Feb 2001 08:22:47 +0000 [thread overview]
Message-ID: <20729.982916567@redhat.com> (raw)
In-Reply-To: <3A957005.3400694E@danielind.com>
vmalik@danielind.com said:
> 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).
Except that the block device is quite a lot of unnecessary overhead (and a
kernel thread, etc.). Reading directly from the MTD device rather than
through either the blockdevice or chardevice would be nicer.
Actually, for 2.4 I'd like to be able to extract a tarball from an MTD
device directly into ramfs rather than ramdisk. CONFIG_BLK_DEV=n
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-02-23 8:22 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
2001-02-23 8:22 ` David Woodhouse [this message]
-- 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=20729.982916567@redhat.com \
--to=dwmw2@infradead.org \
--cc=Vipin.Malik@daniel.com \
--cc=amitc@brocade.com \
--cc=mtd@infradead.org \
--cc=vmalik@danielind.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