From: Gerd Knorr <kraxel@suse.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Alexander E. Patrakov" <patrakov@ums.usu.ru>,
linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: modprobe + request_module() deadlock
Date: Fri, 19 Nov 2004 12:50:42 +0100 [thread overview]
Message-ID: <20041119115042.GA30334@bytesex> (raw)
In-Reply-To: <s5hpt2aayco.wl@alsa2.suse.de>
> > But IMHO Rusty should provide a way to specify those "recommended" install
> > lines in the modules themselves (so that they finally go
> > to /lib/modules/`uname -r`/modules.alias or a similar autogenerated file),
> > like that's already done wih aliases and char-majors.
>
> Well, how about to add a new marker in the driver code such as
>
> MODULE_DEPENDS_ON("somemodule");
>
> so that depmod can pick it up?
Wouldn't work for me as this isn't static. saa7134 has to look at the
hardware, then decide whenever it should load saa7134-empress,
saa7134-dvb or none of them.
On the other hand I don't depend on request_module() waiting for the
modprobe being finished. So maybe we can solve that with a
request_module_async()?
Gerd
next prev parent reply other threads:[~2004-11-19 12:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 22:29 modprobe + request_module() deadlock Johannes Stezenbach
2004-11-18 3:48 ` Rusty Russell
2004-11-18 13:55 ` Johannes Stezenbach
2004-11-18 19:05 ` Takashi Iwai
2004-11-19 4:04 ` Alexander E. Patrakov
2004-11-19 11:10 ` Takashi Iwai
2004-11-19 11:50 ` Gerd Knorr [this message]
2004-11-19 12:42 ` Alexander E. Patrakov
2004-11-21 8:39 ` Rusty Russell
2004-11-22 10:25 ` Gerd Knorr
2004-11-22 14:16 ` Johannes Stezenbach
2004-11-22 14:44 ` Gerd Knorr
2004-11-22 15:36 ` Johannes Stezenbach
2004-11-22 16:52 ` Gerd Knorr
2004-11-24 5:02 ` Rusty Russell
2004-11-24 12:11 ` Gerd Knorr
2004-11-25 16:03 ` Gerd Knorr
2004-11-26 0:34 ` Rusty Russell
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=20041119115042.GA30334@bytesex \
--to=kraxel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=patrakov@ums.usu.ru \
--cc=rusty@rustcorp.com.au \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.