Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rimas Kudelis <rq@akl.lt>
To: ALSA devel <alsa-devel@lists.sourceforge.net>
Cc: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Subject: Re: More detailed Acer (Intel HDA)
Date: Mon, 20 Mar 2006 08:50:14 +0200	[thread overview]
Message-ID: <441E50A6.3030100@akl.lt> (raw)
In-Reply-To: <1142814150.4532.45.camel@mindpipe>

Hola,
>>>> 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...
>>     
> That thread is too long.  Please describe briefly exactly what the
> unexpected behavior is and how you think it should work and file an ALSA
> bug report.
>   

That thread was started long before the acer model was actually added to
hda-intel driver. Everything that I find unexpected is written in the
exact post I linked to.

I'm not going to file a bug. Just asking for Jonathan's opinion about
this (i.e., why doesn't LINE-OUT allow choosing Mic modes, but allows
Line In). After I check everything, i'm willing to write a small patch
that removes all non-working features (like CD and Beep controls) from
the current acer model and, maybe, adds one or two that are not
currently in.

Rimas




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

  reply	other threads:[~2006-03-20  6:50 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
2006-03-20  0:22     ` Lee Revell
2006-03-20  6:50       ` Rimas Kudelis [this message]
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=441E50A6.3030100@akl.lt \
    --to=rq@akl.lt \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=jwoithe@physics.adelaide.edu.au \
    /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