Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Rimas Kudelis <rq@akl.lt>
Cc: ALSA devel <alsa-devel@lists.sourceforge.net>,
	Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Subject: Re: More detailed Acer (Intel HDA)
Date: Wed, 22 Mar 2006 04:38:47 -0500	[thread overview]
Message-ID: <1143020328.1792.66.camel@mindpipe> (raw)
In-Reply-To: <44210F4D.8070508@akl.lt>

On Wed, 2006-03-22 at 10:48 +0200, Rimas Kudelis wrote:
> Hi,
> >>>> On these Acer laptops the evidence thus far indicates that there is no
> >>>> audio connection between the CD drive and the sound card. 
> >>>>         
> >>> I haven't seen any evidence at all, just speculation, apparently no one
> >>> is willing to try Windows to verify this.  Until there's some evidence
> >>> IMHO the CD control should stay.
> >>>       
> >> The fact is that the CD control doesn't work now. And I didn't manage to 
> >> find a way to make any control in the test model influence CD playback 
> >> volume. Why would you want a non-working control to stay?
> >>     
> > Because it may work on some other laptops, and it's better for people to
> > be able to test it.
> >   
> It may or may not work. And people can still use the test model for testing.
> 

Yes exactly, and a missing control is much worse than a control that
does nothing.

There just needs to be some shred of evidence beyond my speculation
about the CD pins not being connected before controls are removed from a
driver.

Lee 



-------------------------------------------------------
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

  parent reply	other threads:[~2006-03-22  9:38 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
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                   ` Lee Revell [this message]
2006-03-21 23:45 ` More detailed Acer (Intel HDA) 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=1143020328.1792.66.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=jwoithe@physics.adelaide.edu.au \
    --cc=rq@akl.lt \
    /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