From: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: alsa-devel@lists.sourceforge.net, Dan Hollis <goemon@anime.net>
Subject: Re: ALSA user documentation
Date: Tue, 28 May 2002 13:21:45 +0900 [thread overview]
Message-ID: <3CF305D9.B987DA79@boosthardware.com> (raw)
In-Reply-To: Pine.LNX.4.44.0205261717520.6800-100000@sasami.anime.net
Dan Hollis wrote:
>
>
> > > Maybe we should integrate this information somewhere?
>
> Well, I hope to design a mechanism in the future where the list is
> automatically generated from the alsa source code...
>
I have been working on a new more automated version of the online docs
and you should probably have a look at that too.
http://www.alsa-project.org/alsa-doc/doc-php/cmipci.php3
I need to figure out how to update the module options for each page from
the source code so that will probably be a similar script to what you
want for the soundcard matrix.
At the moment I am working on getting the add notes pages working
correctly. I think I am half way there then I will move on to the module
options.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
\x1aLINKIFYCbeHGHHcHCHcdGJcCCDCFFBAFIdGIBAGHCdeFeaa
=======================================================================
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
next prev parent reply other threads:[~2002-05-28 4:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 10:10 Re: ALSA user documentation pshirkey
2002-05-27 0:19 ` Dan Hollis
2002-05-27 8:59 ` Martin Langer
2002-05-28 4:21 ` Patrick Shirkey [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-17 1:19 Patrick Shirkey
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=3CF305D9.B987DA79@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=goemon@anime.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.