From: Rimas Kudelis <rq@akl.lt>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>,
alsa-devel@lists.sourceforge.net
Subject: Re: More detailed Acer (Intel HDA)
Date: Mon, 20 Mar 2006 01:19:59 +0200 [thread overview]
Message-ID: <441DE71F.7080209@akl.lt> (raw)
In-Reply-To: <1142793842.4532.28.camel@mindpipe>
[-- Attachment #1: Type: text/plain, Size: 512 bytes --]
Hi,
>> I asked a user on Ubuntu forums to test Acer jack modes more
>> extensively. The results are a bit surprising. You may want to check
>> out http://ubuntuforums.org/showthread.php?p=825101#post825101.
>
> Breezy is too old, that driver had many bugs fixed lately. How does it
> work with the latest ALSA CVS version?
He IS using the latest ALSA CVS version with Breezy. ;) That's why the
sound does work for him. Just some of the details of HOW it works are
quite interesting...
Rimas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2006-03-19 23:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 12:47 More detailed Acer (Intel HDA) Rimas Kudelis
2006-03-19 18:44 ` Lee Revell
2006-03-19 23:19 ` Rimas Kudelis [this message]
2006-03-20 0:22 ` Lee Revell
2006-03-20 6:50 ` Rimas Kudelis
2006-03-20 14:47 ` Takashi Iwai
2006-03-22 0:41 ` Jonathan Woithe
2006-03-22 0:51 ` Lee Revell
2006-03-22 2:41 ` Jonathan Woithe
2006-03-22 7:22 ` Rimas Kudelis
2006-03-22 7:36 ` Lee Revell
2006-03-22 8:48 ` Rimas Kudelis
2006-03-22 9:37 ` Lee Revell
2006-03-22 10:55 ` Rimas Kudelis
2006-03-22 11:01 ` Rimas Kudelis
2006-03-22 11:04 ` Takashi Iwai
2006-03-26 23:36 ` [PATCH] HDA/Realtek: multiple input mux definitions and pin mode additions Jonathan Woithe
2006-03-27 11:53 ` Takashi Iwai
2006-03-27 23:54 ` Jonathan Woithe
2006-03-28 10:47 ` Takashi Iwai
2006-03-22 9:38 ` More detailed Acer (Intel HDA) Lee Revell
2006-03-21 23:45 ` Jonathan Woithe
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=441DE71F.7080209@akl.lt \
--to=rq@akl.lt \
--cc=alsa-devel@lists.sourceforge.net \
--cc=jwoithe@physics.adelaide.edu.au \
--cc=rlrevell@joe-job.com \
/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.