From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Greg KH <greg@kroah.com>
Cc: kaos@ocs.com.au, Linux-Kernel list <linux-kernel@vger.kernel.org>,
quintela@mandrakesoft.com
Subject: Re: modules.pcimap and 8139's
Date: Fri, 14 Dec 2001 18:19:15 -0500 [thread overview]
Message-ID: <3C1A88F3.CE62FB23@mandrakesoft.com> (raw)
In-Reply-To: <3C1A7CA1.D6C119DC@mandrakesoft.com> <20011214151034.A16902@kroah.com>
Greg KH wrote:
>
> On Fri, Dec 14, 2001 at 05:26:41PM -0500, Jeff Garzik wrote:
> > Various tools need to pick "8139cp.c" instead of "8139too.c" based on
> > PCI revision, which is not in modules.pcimap nor struct pci-device-id.
> > grep for 'pci_rev' in both those files to see the PCI revision checks
> > hand-coded currently in the drivers.
> >
> > What is the preferred -2.4- solution?
> >
> > a) append pci rev and mask to the end of each modules.pcimap line, and
> > update struct pci_device_id?
> > b) create new file modules.pci_rev?
> > c) other?
>
> d) ignore it :)
>
> linux-hotplug should try to run modprobe on every module that matches in
> the modules.pcimap table. That way the modules can fight it out for who
> really wants to control the device (I am assuming that the different
> modules know about the pci revision, right?)
>
> modules.pcimap is used to narrow the choices, not necessarily pick the
> "only" choice.
that's ok with me... 8139cp should come first and then error out. Then
(I hope!) 8139too is tried. If that works, all is cool.
But quintela was having a problem with this very thing not working for
him...
Jeff
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
prev parent reply other threads:[~2001-12-14 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-14 22:26 modules.pcimap and 8139's Jeff Garzik
2001-12-14 23:10 ` Greg KH
2001-12-14 23:19 ` Jeff Garzik [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=3C1A88F3.CE62FB23@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=greg@kroah.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=quintela@mandrakesoft.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