Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas GRAZIANO <nicolas.graziano@wanadoo.fr>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] hda driver, correct bug in model "auto"
Date: Thu, 28 Jul 2005 20:32:41 +0200	[thread overview]
Message-ID: <42E924C9.6070602@wanadoo.fr> (raw)
In-Reply-To: <s5hk6jbti30.wl%tiwai@suse.de>

Takashi Iwai a écrit :

>At Wed, 27 Jul 2005 20:32:24 +0200,
>Nicolas GRAZIANO wrote:
>  
>
>>Takashi Iwai a écrit :
>>    
>>
>>>At Tue, 19 Jul 2005 23:34:20 +0200,
>>>Nicolas GRAZIANO wrote:
>>>      
>>>
>>>>- Correct the channels order in model autodetection (not sure of this
>>>>part, I need validation)
>>>>   
>>>>
>>>>        
>>>>
>>>I think this is not correct (although I'm not 100% sure, too).
>>>The association order is front/clfe/surround/side.
>>>(The comment in hda_codec.c is wrong.)
>>>
>>>      
>>>
>>I make the modification because I was thinking than the order was
>>front/clfe/side/back (aka surround ?) and the text on back panel of my
>>motherboard (ASUS P5AD2) make me more confident (with my modification
>>the channels are at the right place). Can we check with an other
>>card/codec ?
>>    
>>
>
>Hmm, interesting.  So, on your board, the association 3 (4th)
>corresponds to a surround jack?
>
>  
>
I am not sure to understand what you mean. 
But perhaps the following information will help.
On the back pannel the inscription are :
Green ()-> Front
Orange ()-> Ctr Bass
Black ()-> Side SPK
Grey ()-> Rear SPK

Extract of the /proc/asound/Intel/codec#0 order by the sequence number
(last byte of Pincap):

Node 0x0b [Pin Complex] wcaps 0x400581: Stereo
  Pincap 0x0833f: IN OUT HP
  Pin Default 0x01014010: [Jack] Line Out at Ext Rear
    Conn = 1/8, Color = Green

Node 0x1f [Pin Complex] wcaps 0x400181: Stereo
  Pincap 0x0833f: IN OUT HP
  Pin Default 0x01016012: [Jack] Line Out at Ext Rear
    Conn = 1/8, Color = Orange

Node 0x0e [Pin Complex] wcaps 0x400581: Stereo
  Pincap 0x081033f: IN OUT HP
  Pin Default 0x01011014: [Jack] Line Out at Ext Rear
    Conn = 1/8, Color = Black

Node 0x20 [Pin Complex] wcaps 0x400181: Stereo
  Pincap 0x0833f: IN OUT HP
  Pin Default 0x01012016: [Jack] Line Out at Ext Rear
    Conn = 1/8, Color = Grey


with my modification :

$speaker-test -D hw:0,0 -c8
 0 - Front Left  --> Green Jack
 4 - Center    --> Orange left
 1 - Front Right  --> Green Jack
 7 - Side Right   --> Black Jack
 3 - Rear Right  --> Grey Jack
 2 - Rear Left   --> Grey Jack
 6 - Side Left  --> Black Jack
 5 - LFE   --> nothing

without  my modification (actual cvs code):

$speaker-test -D hw:0,0 -c8
 0 - Front Left  -->  Green Jack
 4 - Center    --> black Jack
 1 - Front Right  -->  Grenn Jack
 7 - Side Right   -->   nothing
 3 - Rear Right  --> orange Jack
 2 - Rear Left   --> orange Jack
 6 - Side Left  -->  Grey Jack
 5 - LFE   --> black Jack

I hope this information will help.


>Sure, just add a hda_board_config entry for the corresponding pci
>subids.  See patch_realtek.c.
>
>  
>
I try the following path for my ASUS P5AD2 and it's working.
thanks

Nicolas

Index: pci/hda/patch_cmedia.c
===================================================================
RCS file: /cvsroot/alsa/alsa-kernel/pci/hda/patch_cmedia.c,v
retrieving revision 1.11
diff -u -r1.11 patch_cmedia.c
--- pci/hda/patch_cmedia.c      27 Jul 2005 16:25:08 -0000      1.11
+++ pci/hda/patch_cmedia.c      28 Jul 2005 18:22:45 -0000
@@ -647,6 +647,8 @@
        { .modelname = "min_fp", .config = CMI_MIN_FP },
        { .modelname = "full", .config = CMI_FULL },
        { .modelname = "full_dig", .config = CMI_FULL_DIG },
+       { .pci_subvendor = 0x1043, .pci_subdevice = 0x813d, .config =
CMI_FULL_DIG },
+
        { .modelname = "allout", .config = CMI_ALLOUT },
        { .modelname = "auto", .config = CMI_AUTO },
        {} /* terminator */








-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  reply	other threads:[~2005-07-28 18:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 21:34 [PATCH] hda driver, correct bug in model "auto" Nicolas GRAZIANO
2005-07-27  9:37 ` Takashi Iwai
2005-07-27 18:32   ` Nicolas GRAZIANO
2005-07-28  9:06     ` Takashi Iwai
2005-07-28 18:32       ` Nicolas GRAZIANO [this message]
2005-07-29 10:49         ` 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=42E924C9.6070602@wanadoo.fr \
    --to=nicolas.graziano@wanadoo.fr \
    --cc=alsa-devel@alsa-project.org \
    --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