From: "Nicolas Maître" <nimai@skynet.be>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Fwd: Request for HW auto-recognition: HP Pavilion dv7 with STAC92xx
Date: Sat, 15 Dec 2012 23:31:57 +0100 [thread overview]
Message-ID: <CACd4Q03Vy4DBVVM5gyo9NF+aOaBAPoKig8hG7SahMdNhq=smjQ@mail.gmail.com> (raw)
In-Reply-To: <s5hr4mrpqek.wl%tiwai@suse.de>
On Sat, Dec 15, 2012 at 11:21 AM, Takashi Iwai <tiwai@suse.de> wrote:
> So in this case you need to figure out the exact pin configurations on
> your machine. hda_analyzer and hdajackretask programs would be a
> great help for that.
Well, I don't know how to do that efficiently. I have spent some time
trying to play with hda analyzer and hda-jack-retask but I think it
was just a waste of time.
I've used "speaker-test -c 6" as test for each change. Here are my
notes on my attempts to make something work by overriding the pins in
hda-jack-retask, in case is could be useful anyway:
http://pastebin.com/HVgURDuA
I've realized it was probably not the good way to go when I've seen
that the fact that pulseaudio were running actually changed the
mapping.
So, do you know some guide/howto I could follow to do something useful
with my issue?
Thanks.
--
nimai
next prev parent reply other threads:[~2012-12-15 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACd4Q01r1Oa=ds0+eskdkvnMJytuLRj5FPYyNjbdnx5WNWWZvQ@mail.gmail.com>
2012-12-14 21:12 ` Fwd: Request for HW auto-recognition: HP Pavilion dv7 with STAC92xx Nicolas Maître
2012-12-15 10:21 ` Takashi Iwai
2012-12-15 22:31 ` Nicolas Maître [this message]
2012-12-17 2:55 ` Raymond Yau
2012-12-17 14:02 ` Nicolas Maître
2012-12-18 7:50 ` Raymond Yau
2012-12-27 19:02 ` Tomas Pospisek
2012-12-20 0:24 ` Raymond Yau
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='CACd4Q03Vy4DBVVM5gyo9NF+aOaBAPoKig8hG7SahMdNhq=smjQ@mail.gmail.com' \
--to=nimai@skynet.be \
--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;
as well as URLs for NNTP newsgroup(s).