From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Sean Hunter <sean@dev.sportingbet.com>
Cc: kaos@ocs.com.au,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RFC: modules and 2.5
Date: Tue, 03 Jul 2001 03:05:18 -0400 [thread overview]
Message-ID: <3B416EAE.B02C7751@mandrakesoft.com> (raw)
In-Reply-To: <3B415489.77425364@mandrakesoft.com> <20010703075050.B15457@dev.sportingbet.com>
Sean Hunter wrote:
>
> Does this defeat my favourite module-related gothcha, that the machine panics
> if I have (say) a scsi driver builtin to the kernel and the same driver tries
> to load itself as a module?
Other, existing mechanisms should prevent conflicts here. If a builtin
SCSI driver loads successfully, then its calls to request_region,
request_mem_region, or pci_request_regions should have succeeded.
If so, any attempt to grab those I/O regions by another driver,
including another instance of the same driver, should fail.
--
Jeff Garzik | "I respect faith, but doubt is
Building 1024 | what gives you an education."
MandrakeSoft | -- Wilson Mizner
next prev parent reply other threads:[~2001-07-03 7:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 5:13 RFC: modules and 2.5 Jeff Garzik
2001-07-03 6:50 ` Sean Hunter
2001-07-03 7:05 ` Jeff Garzik [this message]
2001-07-03 7:16 ` Keith Owens
2001-07-03 7:24 ` Jeff Garzik
2001-07-03 7:39 ` Keith Owens
2001-07-03 7:44 ` Jeff Garzik
2001-07-03 7:48 ` Fang Han
2001-07-03 7:18 ` Keith Owens
2001-07-03 12:15 ` jlnance
2001-07-06 10:34 ` Rusty Russell
2001-07-07 14:12 ` Jeff Garzik
2001-07-08 7:40 ` Rusty Russell
2001-07-11 22:04 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2001-07-03 17:35 Andrzej Krzysztofowicz
2001-07-03 17:39 ` Jeff Garzik
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=3B416EAE.B02C7751@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sean@dev.sportingbet.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