From: markrages@mlug.missouri.edu
To: Paul Davis <pbd@op.net>
Cc: alsa-devel@alsa-project.org, linux-audio-dev@music.columbia.edu
Subject: Re: initial (incomplete) version of ALSA Audio API tutorial
Date: Fri, 22 Mar 2002 14:53:28 -0600 [thread overview]
Message-ID: <20020322145328.A303@yahoo.com> (raw)
In-Reply-To: <200203212131.g2LLV6b05497@op.net>; from pbd@op.net on Thu, Mar 21, 2002 at 04:31:06PM -0500
On Thu, Mar 21, 2002 at 04:31:06PM -0500, Paul Davis wrote:
> prompted by phil kerr this morning, i started writing a tutorial on
> using the ALSA Audio API (the term "PCM" is OK once you get into this
> stuff, but ...). The following document represents it current state. I
> would like to ask for feedback even though it is very incomplete. I
> have not tested any of the programs yet.
>
There's some small edits I would make. I'll send a patch when you're done with it.
I wish this was a wiki! (there, out of my system, won't say it again, stay calm Kevin...)
The #includes are interpreted as html by Mozilla and don't display.
Line-by-line comments would be a nice way of increasing "tutorial" content.
It's great to see someone who knows what he's doing taking interest in Alsa documentation.
Regards,
Mark
--
Mark Rages
markrages@yahoo.com
http://mlug.missouri.edu/~markrages
The beginning is near.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
prev parent reply other threads:[~2002-03-22 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 21:31 initial (incomplete) version of ALSA Audio API tutorial Paul Davis
2002-03-21 23:28 ` [linux-audio-dev] " Kevin Conder
2002-03-22 1:58 ` Paul Davis
2002-03-22 20:53 ` markrages [this message]
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=20020322145328.A303@yahoo.com \
--to=markrages@mlug.missouri.edu \
--cc=alsa-devel@alsa-project.org \
--cc=linux-audio-dev@music.columbia.edu \
--cc=pbd@op.net \
/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.