All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rimas Kudelis <rq@akl.lt>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Test model
Date: Mon, 20 Feb 2006 07:32:05 +0200	[thread overview]
Message-ID: <43F95455.1030502@akl.lt> (raw)
In-Reply-To: <200602192333.k1JNXCKp018481@auster.physics.adelaide.edu.au>

Hello,

> Note that this has nothing to do with the inability to make the internal
> speaker play ball on your laptop - it affects only the ability to record
> from certain widgets via the second ADC (0x05) since the existing capture list
> is for NID 0x04.

I know that. BTW one of the actions I tried last weekend was recording 
something from the microphone. And it failed too. selecting one (don't 
remember which, though) of the capture channels for capture resulted 
in continuous noise being recorded, and selecting the other one 
resulted in silence. Also, selecting both resulted in sum of these, 
hence, noise again...

Also, not sure if it's alsamixer's or driver's fault, alsamixer always 
says "Input Source 1" is "1", even though it selects the required source.

Paulo, would you please confirm this too?

Jonathan, I think that maybe the "test" model should have even more 
controls to play with, even those that may seem like should never be 
used? For example, there seem to be no checkboxes or something similar 
to control S/PDIF NIDs, or jack (pin) widgets and so on. Such controls 
might be useful for testing, when nothing else seems to work out, like 
the Acer case at the moment. In order not to clutter the default 
tester's mixer interface, maybe this (at least partially) should go to 
some kind of an "extended test" model, i don't know.

BTW, if I haven't misunderstood the datasheet, I think it says that 
S/PDIF NIDs (0x03 and 0x06, if I remember correctly) can be told to 
output Analog audio, along with the other channels. Could this 
possibly be Acer's case? I'm asking this because these were probably 
the only NIDs that I didn't even try to play with...

Best regards,

Rimas



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

  reply	other threads:[~2006-02-20  5:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 22:49 Test model Rimas Kudelis
2006-02-15 23:48 ` Jonathan Woithe
2006-02-16  9:29   ` Rimas Kudelis
2006-02-16 10:05     ` Rimas Kudelis
2006-02-17  2:05       ` Jonathan Woithe
2006-02-16 10:08     ` Paulo Matias
2006-02-16 16:52       ` Rimas Kudelis
2006-02-17  2:14         ` Jonathan Woithe
2006-02-17  2:12       ` Jonathan Woithe
2006-02-17  1:59     ` Jonathan Woithe
2006-02-17 12:07       ` Rimas Kudelis
2006-02-17 12:57         ` Paulo Matias
2006-02-17 13:17           ` Rimas Kudelis
2006-02-17 18:18             ` Rimas Kudelis
2006-02-17 18:24               ` Paulo Matias
2006-02-17 18:36                 ` Rimas Kudelis
2006-02-20  0:44           ` Jonathan Woithe
2006-02-17 18:40         ` Paulo Matias
2006-02-20  0:27         ` Jonathan Woithe
2006-02-19 17:05       ` Rimas Kudelis
2006-02-19 23:33         ` Jonathan Woithe
2006-02-20  5:32           ` Rimas Kudelis [this message]
2006-02-20  6:32             ` Jonathan Woithe
2006-02-20  7:13               ` Rimas Kudelis
2006-02-20 23:17                 ` Jonathan Woithe
2006-02-21 10:17                   ` Rimas Kudelis
2006-02-21 23:20                     ` Jonathan Woithe
2006-02-22  6:40                       ` Rimas Kudelis
2006-02-22 23:50                         ` 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=43F95455.1030502@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 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.