From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Paul Davis <pbd@op.net>
Cc: alsa-devel@lists.sourceforge.net, goemon@anime.net
Subject: Re: ALSA docs
Date: Tue, 30 Jul 2002 04:12:20 +0900 [thread overview]
Message-ID: <3D459394.80104@boosthardware.com> (raw)
In-Reply-To: E17ZEzS-0001Sf-00@usw-sf-list1.sourceforge.net
Paul Davis wrote:
>>Do you mean that I should be parsing each driver file seperately?
>
>
> not really, just do a single pass over each one of them at some point
> in time. store the results, and use them. this should get you started
> (its not perfect, but it doesn't do a bad job.
>
> #!/usr/local/bin/perl
>
> while(<>) {
> if (/MODULE_PARM_DESC/) {
> @foo = split /[()]/;
> @bar = split (/,/, $foo[1], 2);
> $bar[1] =~ s/"//g;
> printf ("%-32s %s\n", $bar[0], $bar[1]);
> }
> }
>
> add something to recurse through the source tree, and include the
> module name and card name info, and you're pretty much done ...
>
Now that I think about it I could probably get away with doing this on
my computer everytime that a new driver is added. We have to add the
info manually for the soundcard matrix anyway.
Although If I don't have access to a working Linux computer in the
future this will cause problems. Ideally I would like a way to do this
all from online preferably automagically.
I'm loathe to admit but I am very new to perl so I don't even know how
to call the above code from a webpage. Is it possible to get the perl
script to parse the files and then use php to parse the output of the
perl script? I have various variables from a form which php can
understand and use to create the correct output in the template.
Unless Dan Hollis speaks up soon (I tried to contact him last Friday)
I'm officially commandeering the Soundcard matrix from his dir and
putting it in the alsa-docs dir. Where it will become the opening page
to the driver docs. He will need to get cvs access for the www dir from
Jaroslav to edit the new version of the matrix.
You can see what I'm trying to do here:
http://www.alsa-project.org/alsa-doc/ALSA_Soundcard_Matrix.php3
That is unless other people have a better idea for how to make the docs
more user friendly (and competitive ;] ).
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
next prev parent reply other threads:[~2002-07-29 19:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 16:17 ALSA docs Patrick Shirkey
2002-07-19 17:39 ` Takashi Iwai
2002-07-21 6:40 ` Patrick Shirkey
2002-07-25 16:20 ` Patrick Shirkey
2002-07-25 16:32 ` Paul Davis
2002-07-25 17:03 ` Patrick Shirkey
2002-07-25 17:51 ` Patrick Shirkey
2002-07-27 0:15 ` Paul Davis
2002-07-29 4:38 ` Patrick Shirkey
2002-07-29 12:08 ` Paul Davis
2002-07-29 17:55 ` Patrick Shirkey
2002-07-29 18:12 ` Paul Davis
2002-07-29 19:12 ` Patrick Shirkey [this message]
2002-07-29 20:25 ` Patrick Shirkey
2002-07-27 0:20 ` Paul Davis
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=3D459394.80104@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=goemon@anime.net \
--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.