From: Lee Revell <rlrevell@joe-job.com>
To: Anderson Briglia <briglia.anderson@gmail.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Testing framework
Date: Sun, 15 Jan 2006 18:35:51 -0500 [thread overview]
Message-ID: <1137368151.25801.119.camel@mindpipe> (raw)
In-Reply-To: <e55525570601151455v537dffdhe37befc992499b5a@mail.gmail.com>
On Sun, 2006-01-15 at 18:55 -0400, Anderson Briglia wrote:
> Hi all,
>
> Is there some testing framework for testing newer ALSA drivers? I've
> been using speaker-test and aplay, from alsa-utils package but I think
> it could be automated or give more specific results.
How would you test whether sound is coming out (no sound is by far the
most common sympton of incomplete hardware support) other than listening
to it?
It really depends what you want to test.
Lee
-------------------------------------------------------
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2006-01-15 23:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 22:55 Testing framework Anderson Briglia
2006-01-15 23:35 ` Lee Revell [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-28 13:18 Karuna sagar k
2007-04-22 20:46 Karuna sagar K
2007-04-23 9:09 ` Kalpak Shah
2007-04-23 11:25 ` Karuna sagar K
2007-04-23 14:04 ` Avishay Traeger
2007-04-23 22:11 ` Ric Wheeler
2007-04-25 11:28 ` Karuna sagar K
2007-04-28 9:35 ` Pavel Machek
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=1137368151.25801.119.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=briglia.anderson@gmail.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.