Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Shane <shane-alsa@cm.nu>,
	alsa-user@lists.sourceforge.net,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [Alsa-devel] Re: Line-in not working on Audigy2
Date: Mon, 07 Nov 2005 10:51:23 -0500	[thread overview]
Message-ID: <1131378684.8383.14.camel@mindpipe> (raw)
In-Reply-To: <s5hd5lcpkpu.wl%tiwai@suse.de>

On Mon, 2005-11-07 at 15:59 +0100, Takashi Iwai wrote:
> At Sat, 05 Nov 2005 16:27:14 -0500,
> Lee Revell wrote:
> > 
> > On Sat, 2005-11-05 at 12:41 -0800, Shane wrote:
> > > On Sat, Nov 05, 2005 at 03:30:11PM -0500, Lee Revell wrote:
> > > > > The card:
> > > > > 0000:03:00.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
> > > > >         Subsystem: Creative Labs: Unknown device 2006
> > > > 
> > > > This is probably just a driver bug.  Subsystem 2006 is not in the list
> > > > of PCI IDs.
> > > > 
> > > > Can you please provide name and the model number of the card.  This will
> > > > be something like "Audigy 2 ZS", model "SB0350".  This information may
> > > > be on the box, the card, or you can obtain it from the Windows driver.
> > > 
> > > Hmm, pulling this machine apart may take some time.  Is
> > > there any way to query the card in software under Linux. 
> > > Not sure if it helps but oss emu10k1 gives this:
> > > ACPI: PCI interrupt for device 0000:03:00.0 disabled
> > > Creative EMU10K1 PCI Audio Driver, version 0.20a, 16:12:50
> > > Nov  1 2005
> > > ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low)
> > > -> IRQ 169
> > > emu10k1: Audigy rev 4 model 0x2006 found, IO at
> > > 0xdc80-0xdcbf, IRQ 169
> > > 
> > > Could something like libdiscover or hotplug provide the
> > > model number?
> > > 
> > 
> > Try this patch.
> > 
> > Summary: Add support for Audigy 2 subsystem 2006.
> > 
> > Signed-Off-By: Lee Revell <rlrevell@joe-job.com>
> 
> FYI, I applied it to CVS now.  Thanks.
> 

It would be a big help if someone has time to write a perl script to
extract the PCI ID -> name and model number mapping from the Windows
drivers, http://www.kxproject.com, and generate the hardware features
table.  Email me privately and I'll send you the .inf file.

Lee



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php

  reply	other threads:[~2005-11-07 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051104234906.GA7479@cm.nu>
     [not found] ` <1131222612.13627.26.camel@mindpipe>
     [not found]   ` <20051105204154.GA2134@cm.nu>
2005-11-05 21:27     ` Line-in not working on Audigy2 Lee Revell
2005-11-07 14:59       ` Re: [Alsa-user] " Takashi Iwai
2005-11-07 15:51         ` Lee Revell [this message]
     [not found]           ` <20051121190023.GA2783@cm.nu>
2005-11-21 19:38             ` [Alsa-devel] " Peter Zubaj

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=1131378684.8383.14.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=shane-alsa@cm.nu \
    --cc=tiwai@suse.de \
    /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