From: David Woodhouse <dwmw2@infradead.org>
To: Vipin Malik <Vipin.Malik@daniel.com>
Cc: "''mtd@infradead.org' '" <mtd@infradead.org>
Subject: Re: Unable to mount compressed root f/s because init_mtd() does n ot r egister block device!
Date: Thu, 22 Feb 2001 08:08:51 +0000 [thread overview]
Message-ID: <12716.982829331@redhat.com> (raw)
In-Reply-To: <30724FF712DFD2119E6200104B2448920119744B@mail1>
Vipin.Malik@daniel.com said:
> Ok, looking a bit more at it, it seems that all the init for the mtd
> stuff is happening when do_inicalls() gets called as they are all
> declared as initcalls.
> But looking at the other block device stuff (hd, floppy etc.) they all
> get init'ed by calling blk_dev_init() from genhd.c which gets called
> by device_setup() called from init/main.c
>
> This guarantees that the block devices are registered before the
> ramdisk load stuff gets called, hence allowing them to be used to load
> compressed filesystems.
> How to we fix this (as I'm not too familiar with the init stuff and
> how to change that)?
Either we stop using initcalls for the MTD stuff in 2.2.18 - just revert to
the old method as we did in earlier 2.2, or we fix the remainder of 2.2.19
to use initcalls properly. Probably the former.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-02-22 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 5:26 Unable to mount compressed root f/s because init_mtd() does n ot r egister block device! Vipin Malik
2001-02-22 8:08 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-22 13:11 Vipin Malik
2001-02-22 13:18 ` David Woodhouse
2001-02-22 19:22 ` Vipin Malik
2001-02-22 19:00 ` David Woodhouse
2001-02-22 20:18 ` Vipin Malik
2001-02-22 21:32 ` Vipin Malik
2001-02-22 21:55 ` 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=12716.982829331@redhat.com \
--to=dwmw2@infradead.org \
--cc=Vipin.Malik@daniel.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