From: Jens Axboe <axboe@suse.de>
To: A Duston <hald@sound.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bio and "old" block drivers
Date: Wed, 12 Dec 2001 16:29:28 +0100 [thread overview]
Message-ID: <20011212152928.GC9324@suse.de> (raw)
In-Reply-To: <Pine.GSO.4.10.10112111539180.5913-100000@sound.net> <20011212101957.GE7562@suse.de> <3C177767.8132794F@sound.net>
In-Reply-To: <3C177767.8132794F@sound.net>
On Wed, Dec 12 2001, A Duston wrote:
> Jens Axboe wrote:
> >
> > On Tue, Dec 11 2001, Hal Duston wrote:
> > > I'm looking at the bio changes for ps2esdi. The driver
> > > appears to no longer work compiled when into the kernel.
> > > The ps2esdi_init call has been removed from
> > > ll_rw_blk.c:blk_dev_init. Where is the new/correct place
> > > to call this from? This appears to be the same way with
> > > many of the other "old" block drivers as well.
> >
> > Just use module_init to make this happen automagically.
>
> Sorry, I am not understanding you here. Could you spell it
> out please? My root filesystem is on the ps2esdi disk, do
> I need to set up an initrd, and load the ps2esdi driver as
> a module? Or do you mean that I should change things to
> have module_init call it even when it isn't built as a
> module? Or something else?
I mean:
--- /opt/kernel/linux-2.5.1-pre10/drivers/block/ps2esdi.c Tue Dec 11 13:30:36 2001
+++ drivers/block/ps2esdi.c Wed Dec 12 10:26:09 2001
@@ -189,6 +189,8 @@
return 0;
} /* ps2esdi_init */
+module_init(ps2esdi_init);
+
#ifdef MODULE
static int cyl[MAX_HD] = {-1,-1};
and then it will be initialized correctly. module_init isn't specific to
modules, it will work for builtin stuff too. See __initcall
--
Jens Axboe
prev parent reply other threads:[~2001-12-12 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 21:40 bio and "old" block drivers Hal Duston
2001-12-12 10:19 ` Jens Axboe
2001-12-12 15:27 ` A Duston
2001-12-12 15:29 ` Jens Axboe [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=20011212152928.GC9324@suse.de \
--to=axboe@suse.de \
--cc=hald@sound.net \
--cc=linux-kernel@vger.kernel.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