From: Ben Hutchings <bhutchings@solarflare.com>
To: Pascal Terjan <pterjan@mandriva.com>
Cc: netdev@vger.kernel.org
Subject: Re: 8139cp vs 8139too, request_module ?
Date: Wed, 10 Jun 2009 18:00:06 +0100 [thread overview]
Message-ID: <1244653206.2848.15.camel@achroite> (raw)
In-Reply-To: <1244649729.14601.1.camel@plop>
On Wed, 2009-06-10 at 18:02 +0200, Pascal Terjan wrote:
> Hello,
> 8139cp and 8139too both handle the same id and then test revision.
>
> If revision is wrong they tell to load the other module and return
> ENODEV.
>
> Why not doing a request_module instead of printing a message ?
The kernel requests a module to handle each PCI device it doesn't
already have a driver for. modprobe will then load all modules that
match that PCI device and vendor id. So 8139cp and 8139too are both
loaded for PCI devices that might be handled by either. There is no
need for them to try to load each other, and I suspect there would be a
risk of deadlock if they did.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2009-06-10 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 16:02 8139cp vs 8139too, request_module ? Pascal Terjan
2009-06-10 17:00 ` Ben Hutchings [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=1244653206.2848.15.camel@achroite \
--to=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=pterjan@mandriva.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;
as well as URLs for NNTP newsgroup(s).