All of lore.kernel.org
 help / color / mirror / Atom feed
From: wwp <subscript@free.fr>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Audigy4 support
Date: Fri, 24 Feb 2006 19:58:35 +0100	[thread overview]
Message-ID: <20060224195835.457552d8@localhost.localdomain> (raw)
In-Reply-To: <s5hd5hcvcjx.wl%tiwai@suse.de>

[-- Attachment #1: Type: text/plain, Size: 4708 bytes --]

Hello Takashi,


On Fri, 24 Feb 2006 19:25:54 +0100 Takashi Iwai <tiwai@suse.de> wrote:

> At Wed, 22 Feb 2006 19:40:29 +0100,
> wwp wrote:
> > 
> > [1  <multipart/mixed (7bit)>]
> > [1.1  <text/plain; US-ASCII (quoted-printable)>]
> > Hello all,
> > 
> > 
> > I've got a brand new Audigy4 PCI sound-card, running on Debian unstable
> > (kernel 2.6.15, feat. Alsa 1.0.10+1.0.11-rc2-2).
> > 
> > I'm able to get PCM out but can't get line-in to work: the alsa mixer
> > allows un-muting line-in but I can't get the input selector in audacity
> > for instance.
> > 
> > 
> > The exact model is a Creative SoundBlaster Audigy 4 retail (purchase date:
> > 20060219, UK) w/ remote controler RM-1500.
> > 
> > 0000:00:0a.0 0401: 1102:0008
> > Here was lspci says:
> > 
> > 0000:00:0a.0 Multimedia audio controller: Creative Labs SB0400 Audigy2
> > Value Subsystem: Creative Labs: Unknown device 1021
> > 		 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
> > VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF-
> > FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > Latency: 32 (500ns min, 5000ns max) Interrupt: pin A routed to IRQ 12
> > 		 Region 0: I/O ports at d400 [size=64]
> > 		 Capabilities: [dc] Power Management version 2
> > 				 Flags: PMEClk- DSI+ D1+ D2+
> > AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable-
> > DSel=0 DScale=0 PME-
> > 
> > 
> > I've found that the emu10k1 sources (checked at 1.0.11-rc3) don't include
> > the card IDs, would the attached patch do it? Would that one be enough to
> > get proper line-in support?
> 
> Are you sue that the patch really works for you?
> 1102:2008 are _not_ subsystem IDs but the normal PCI IDs.
> 
> The subsystem number in the emu10k1's chip table is what you get as
> the serial number in /proc/asound/cards (perhaps 0x10211102).

Well, I never said that the patch worked neither that I've applied it :-).
No, I just wrote it as I assumed, wrongly, that it was a possible solution to
submit before I set up a customized kernel configuration from the sources.
Sorry for this confusion.

Here's what `cat /proc/asound/cards` shows:

0 [Audigy2        ]: Audigy2 - Audigy 2 Value [Unknown]
                     Audigy 2 Value [Unknown] (rev.0, serial:0x10211102) at 0xd400, irq 12
1 [UART           ]: MPU-401 UART - MPU-401 UART
                     MPU-401 UART at 0x330, irq 5


Now.. what to do? Should I provide more information? What to expect?


> > BTW, is it normal that the chip_detail table shows .id Audigy2 for Audigy4
> > cards? Is emu10k1 falling back to Audigy2 Value when it doesn't know the
> > exact card IDs?
> 
> It's correct behavior.  "Audigy2" is just the driver model name.  As
> long as Audigy4 uses the same configuration as Audigy2, there is no
> reason to introduce a new incompatibility.

Thanks for this clarification!
 

Regards,

> > Here are some references more:
> > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1868
> > http://www.creative.com/products/product.asp?category=1&subcategory=434&product=14103
> > 
> > 
> > Regards,
> > 
> > -- 
> > wwp
> > [1.2 alsa-driver-1.0.11rc3-audigy4-sb0400.diff <text/x-patch
> > (quoted-printable)>] --- emu10k1_main.c.orig	2006-02-22
> > 18:24:06.000000000 +0100 +++ emu10k1_main.c	2006-02-22
> > 18:24:12.000000000 +0100 @@ -824,6 +824,16 @@
> >  	 .emu10k2_chip = 1,
> >  	 .ca0102_chip = 1,
> >  	 .emu1212m = 1} ,
> > +	/* Tested by claws 22nd February 2006 */
> > +	{.vendor = 0x1102, .device = 0x0004, .subsystem = 0x20081102,
> > +	 .driver = "Audigy2", .name = "Audigy 4 [SB0400]", 
> > +	 .id = "Audigy2",
> > +	 .emu10k2_chip = 1,
> > +	 .ca0102_chip = 1,
> > +	 .ca0151_chip = 1,
> > +	 .spk71 = 1,
> > +	 .spdif_bug = 1,
> > +	 .ac97_chip = 1} ,
> >  	/* Tested by James@superbug.co.uk 3rd July 2005 */
> >  	{.vendor = 0x1102, .device = 0x0004, .subsystem = 0x20071102,
> >  	 .driver = "Audigy2", .name = "Audigy 4 PRO [SB0380]", 
> > --- p16v.c.orig	2005-12-22 18:01:20.000000000 +0100
> > +++ p16v.c	2006-02-22 18:24:46.000000000 +0100
> > @@ -118,6 +118,7 @@
> >   * Class 0401: 1102:0004 (rev 04) Subsystem: 1102:1007 -> Audigy2 6.1
> > Model:SB0240
> >   * Class 0401: 1102:0004 (rev 04) Subsystem: 1102:1002 -> Audigy2
> > Platinum  Model:SB msb0240230009266
> >   * Class 0401: 1102:0004 (rev 04) Subsystem: 1102:2007 -> Audigy4 Pro
> > Model:SB0380 M1SB0380472001901E
> > + * Class 0401: 1102:0004 (rev 04) Subsystem: 1102:2008 -> Audigy4
> > Model:SB0400 *
> >   */
> >  
> > [2 signature.asc <application/pgp-signature (7bit)>]
> > 
> 


-- 
wwp

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-02-24 18:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 18:40 Audigy4 support wwp
2006-02-22 19:11 ` Lee Revell
2006-02-22 20:02   ` wwp
2006-02-24 18:25 ` Takashi Iwai
2006-02-24 18:58   ` wwp [this message]
2006-02-24 19:02     ` Takashi Iwai
2006-02-25 11:01       ` wwp
2006-02-27 11:33         ` Takashi Iwai

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=20060224195835.457552d8@localhost.localdomain \
    --to=subscript@free.fr \
    --cc=alsa-devel@lists.sourceforge.net \
    --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 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.