All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: sound and scsi pci MODULE_DEVICE_TABLE entries? (primary for Alan  Cox)
Date: Sat, 18 Nov 2000 01:17:58 -0500	[thread overview]
Message-ID: <3A161F16.89206974@mandrakesoft.com> (raw)
In-Reply-To: <200011180601.WAA01562@adam.yggdrasil.com>

"Adam J. Richter" wrote:
> Hello Alan,
> 
>         Jeff Garzik tells me that you, with some help from some other
> kernel developers, are hacking on the sound drivers right now.  I
> would like to add PCI MODULE_DEVICE_TABLE entries to three of
> the four PCI sound drivers: cmpci, cs46xx and nm256_audio.
> (I have already sent a similar patch to Zach Brown for maestro,
> although that was a port to the new PCI interface.)  This will
> enable depmod to record the PCI ID's that they care about in
> /lib/modules/<version>/modules.pcimap, which, in turn, will
> enable more automated module loading based on hardware configuration.

I responded to Adam in private, but wanted to speak up in public too: 
these changes sound ok with me.  The patches change no code logic, they
export the supported PCI ids to userspace, and make the transition to
the new PCI API a tiny bit easier.

	Jeff


-- 
Jeff Garzik             |
Building 1024           | The chief enemy of creativity is "good" sense
MandrakeSoft            |          -- Picasso
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-18  6:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-18  6:01 sound and scsi pci MODULE_DEVICE_TABLE entries? (primary for Alan Cox) Adam J. Richter
2000-11-18  6:17 ` Jeff Garzik [this message]
2000-11-18 18:07 ` Christoph Hellwig

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=3A161F16.89206974@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=adam@yggdrasil.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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.