public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: kaos@ocs.com.au
Cc: Linux-Kernel list <linux-kernel@vger.kernel.org>
Subject: modules.pcimap and 8139's
Date: Fri, 14 Dec 2001 17:26:41 -0500	[thread overview]
Message-ID: <3C1A7CA1.D6C119DC@mandrakesoft.com> (raw)

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?

Distros at least need to solve this for 2.4...

-- 
Jeff Garzik      | Only so many songs can be sung
Building 1024    | with two lips, two lungs, and one tongue.
MandrakeSoft     |         - nomeansno

             reply	other threads:[~2001-12-14 22:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-14 22:26 Jeff Garzik [this message]
2001-12-14 23:10 ` modules.pcimap and 8139's Greg KH
2001-12-14 23:19   ` 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=3C1A7CA1.D6C119DC@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /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