Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Patrice Tisserand <Patrice.Tisserand@ircam.fr>
Cc: Free Ekanayaka <free@centrotemporeale.it>,
	alsa-devel@lists.sourceforge.net
Subject: Re: Cards PCI ids
Date: Tue, 05 Nov 2002 18:29:48 +0100	[thread overview]
Message-ID: <s5hlm479b77.wl@alsa2.suse.de> (raw)
In-Reply-To: <1036423472.9417.75.camel@localhost.localdomain>

At 04 Nov 2002 16:24:31 +0100,
Patrice Tisserand wrote:
> 
> On Mon, 2002-11-04 at 15:35, Free Ekanayaka wrote:
> > 
> > Hi,
> > 	I'd like to modify the discover library
> > (http://hackers.progeny.com/discover) to use ALSA
> > modules names instead of OSS ones when detecting sound devices.
> > 
> > Is there a place where I can found a mapping like:
> > 
> > soundcard PCI Id ---> ALSA module name
> > 
> > ?
> > 
> Hi, 
> I don't know where you can find a such mapping, but maybe you can
> extract it from drivers source code.
> As far as I know, each pci driver contains a pci_device_id array
> initialize with VENDOR_ID and DEVICE_ID of supported pci device.
> 
> For example, if you look into ens1370.c you will find:
> static struct pci_device_id snd_audiopci_ids[] __devinitdata = {
> #ifdef CHIP1370
>         { 0x1274, 0x5000, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
> ES1370 */
> #endif
> #ifdef CHIP1371
>         { 0x1274, 0x1371, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
> ES1371 */
>         { 0x1274, 0x5880, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
> ES1373 - CT5880 */
>         { 0x1102, 0x8938, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /*
> Ectiva EV1938 */
> #endif
>         { 0, }
> };
> 
> I hope it will help you.

or, you can check the file /lib/modules/VERSION/modules.pcimap,
which holds the all entries for pci modules (although it's a bit
cryptic :)


Takashi


-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en

  reply	other threads:[~2002-11-05 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-03 20:49 Audigy and ac3-passthrough not working Pasi Kärkkäinen
2002-11-04  9:18 ` Takashi Iwai
2002-11-04 14:35   ` Cards PCI ids Free Ekanayaka
2002-11-04 15:24     ` Patrice Tisserand
2002-11-05 17:29       ` Takashi Iwai [this message]
2002-11-06 11:27         ` Free Ekanayaka

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=s5hlm479b77.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=Patrice.Tisserand@ircam.fr \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=free@centrotemporeale.it \
    /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