From: Gerd Knorr <kraxel@suse.de>
To: Johannes Stezenbach <js@convergence.de>,
Gerd Knorr <kraxel@suse.de>, Johannes Stezenbach <js@linuxtv.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Takashi Iwai <tiwai@suse.de>,
"Alexander E. Patrakov" <patrakov@ums.usu.ru>,
linux-kernel@vger.kernel.org
Subject: Re: modprobe + request_module() deadlock
Date: Mon, 22 Nov 2004 17:52:01 +0100 [thread overview]
Message-ID: <20041122165201.GA2060@bytesex> (raw)
In-Reply-To: <20041122153637.GA10673@convergence.de>
> > I can fix that in the driver, by delaying the request_module() somehow
> > until the saa7134 module initialization is finished. I don't think that
> > this is a good idea through as it looks like I'm not the only one with
> > that problem ...
>
> Delaying request_module() sounds ugly. Anyway, if you can
> get it to work reliably...
I think I can, havn't tried yet through.
> Actually dvb-bt8xx.ko has a similar problem (no hotplug for DVB). It
> uses bttv_sub_register(), though, but this doesn't do probing
> and the PCI ids have to be in bttv-cards.c. It would be nicer
> if dvb-bt8xx.ko could use a similar mechanism as dvb-ttpci.ko.
Well, you can use the second PCI function.
> Or do you plan to add request_module("dvb-bt8xx") in bttv-driver.c?
I can do that as well, bttv knows anyway which ones are dvb cards and
which ones are not.
> And how about cx88 (I haven't checked this)?
cx88-dvb has a PCI ID table. The cx2388x has a separate PCI function
for the MPEG stuff which makes it a bit easier to get that handled
by hotplug directly ;)
Gerd
next prev parent reply other threads:[~2004-11-22 17:10 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
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 [this message]
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=20041122165201.GA2060@bytesex \
--to=kraxel@suse.de \
--cc=js@convergence.de \
--cc=js@linuxtv.org \
--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.