From: Takashi Iwai <tiwai@suse.de>
To: mariook@wp.pl
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] Asus A6RP and ALC861 headphones problem solved
Date: Mon, 09 Oct 2006 15:31:35 +0200 [thread overview]
Message-ID: <s5hlknpr4y0.wl%tiwai@suse.de> (raw)
In-Reply-To: <005701c6eb15$be16e590$83030a54@MIREK>
At Sun, 8 Oct 2006 22:10:02 +0200,
<mariook@wp.pl> wrote:
>
> Hi!
>
> I finally made it, now can use headphones with my laptop :)
>
> My last thread (started on 23 Sep 20:08) about my problem is quite long, so
> I decided to make a new one with result of my work - patched patch_realtek.c
> file.
>
> The patch I posted least time was good. The only thing that had to be
> changed is to remove this line:
> .need_dac_fix = 1,
> from alc861_presets. With this line of code the patch doesn't want to work.
This implies that the headphone jack is connected to another DAC, most
likely the side one (0x04). The right fix would to add .hp_nid = 0x04
in the preset table. If 0x04 doesn't work, try 0x05 or 0x06 instead.
> There is only one thing that I'm not sure...
> When channel mode is changed to 6ch the sound is in built-in speakers,
> line-in jack and mic jack, but not in hp jack (of course when i plug
> something to hp jack the sound in built-in speakers disappears). Is that
> correct?
>
> Because each time I make a patch file it doesn't want to work (I make it
> with this command: diff -Nuar old.file new.file), I'm sending in attachment
> compressed patch_realtek.c file (I patched final version 1.0.13 of
> patch_realtek.c). The only important changes are those connected with
> asus-a6rp model, please ignore changes made in parts of code connected with
> other models.
Oh no, please send a patch instead. Otherwise we cannot review and
check your changes.
What do you mean "it doesn't want to work"? If you changed a single
file, you can just create a diff for that file, simply by
diff -u orig-alsa-kernel/pci/hda/patch_realtek.c \
new-alsa-kernel/pci/hda/patch_realtek.c
Takashi
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-10-09 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-08 20:10 [PATCH] Asus A6RP and ALC861 headphones problem solved mariook
2006-10-09 13:31 ` Takashi Iwai [this message]
2006-10-11 16:36 ` mariook
2006-10-11 16:45 ` Takashi Iwai
2006-10-17 18:56 ` Takashi Iwai
2006-10-19 22:10 ` mariook
2006-10-19 23:39 ` Tobin Davis
2006-10-20 13:33 ` Takashi Iwai
2006-10-20 20:21 ` mariook
2006-10-23 12:11 ` 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=s5hlknpr4y0.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mariook@wp.pl \
/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.