All of lore.kernel.org
 help / color / mirror / Atom feed
From: wwp <subscript@free.fr>
To: alsa-devel@lists.sourceforge.net
Subject: Audigy4 support
Date: Wed, 22 Feb 2006 19:40:29 +0100	[thread overview]
Message-ID: <20060222194029.1709b043@localhost.localdomain> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1674 bytes --]

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?

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?


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: alsa-driver-1.0.11rc3-audigy4-sb0400.diff --]
[-- Type: text/x-patch; name=alsa-driver-1.0.11rc3-audigy4-sb0400.diff, Size: 1206 bytes --]

--- 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
  *
  */
 

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

             reply	other threads:[~2006-02-22 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 18:40 wwp [this message]
2006-02-22 19:11 ` Audigy4 support Lee Revell
2006-02-22 20:02   ` wwp
2006-02-24 18:25 ` Takashi Iwai
2006-02-24 18:58   ` wwp
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=20060222194029.1709b043@localhost.localdomain \
    --to=subscript@free.fr \
    --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 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.