Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arcady Genkin <agenkin-lst-alsa-devel@thpoon.com>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Re: Audigy 2 support - update
Date: Sat, 24 May 2003 22:13:40 -0400	[thread overview]
Message-ID: <863cj3vkmj.fsf@tea.thpoon.com> (raw)
In-Reply-To: <3ECFD2BC.1000307@superbug.demon.co.uk> (James Courtier-Dutton's message of "Sat, 24 May 2003 21:14:52 +0100")

James Courtier-Dutton <James@superbug.demon.co.uk> writes:

> As you can see, 0x1102, 0x0002 is my SB Live.
> Add a extra line for your Audigy 2 platinum ex.
>
> and recompile, and see if that helps.

It seems that there already is a line for my card:

,----[ lspci output ]
| 02:05.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
| 02:05.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 04)
| 02:05.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)
`----

,----[ lspci -r output ]
| 02:05.0 Class 0401: 1102:0004 (rev 04)
| 02:05.1 Class 0980: 1102:7003 (rev 04)
| 02:05.2 Class 0c00: 1102:4001 (rev 04)
`----

So, according to your instructions, my card should be identified by
"Class 0401: 1102:0004", but there already is a line for that in
alsa-kernel/pci/emu10k1/emu10k1.c:

{ 0x1102, 0x0004, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 1 },    /* Audigy */

Am I missing something?  Thanks a lot for your reply!
-- 
Arcady Genkin

guilt is the cause of more disauders
than history's most obscene marorders (E.E. Cummings)


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

  reply	other threads:[~2003-05-25  2:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23  5:12 Audigy 2 support - update Stephen Hassard
2003-05-23  5:36 ` Stephen Hassard
2003-05-23  7:30 ` Florin Andrei
2003-05-23  8:33   ` Måns Rullgård
2003-05-24  3:39     ` Florin Andrei
2003-05-24 16:59       ` Stephen Hassard
2003-05-24 18:47         ` Arcady Genkin
2003-05-24 20:14           ` James Courtier-Dutton
2003-05-25  2:13             ` Arcady Genkin [this message]
2003-05-23 14:46   ` Stephen Hassard
2003-05-24  0:43   ` Stephen Hassard
2003-05-24  3:37     ` Florin Andrei
2003-05-24 13:13       ` James Courtier-Dutton
2003-05-27  7:28         ` Pasi Kärkkäinen
2003-07-07 18:49           ` Pasi Kärkkäinen
2003-05-24  3:44 ` Florin Andrei
2003-05-24 16:49   ` Stephen Hassard
  -- strict thread matches above, loose matches on Subject: below --
2003-05-25  2:27 maniacdavid

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=863cj3vkmj.fsf@tea.thpoon.com \
    --to=agenkin-lst-alsa-devel@thpoon.com \
    --cc=James@superbug.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    /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