Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA docs
Date: Tue, 30 Jul 2002 05:25:06 +0900	[thread overview]
Message-ID: <3D45A4A2.5010602@boosthardware.com> (raw)
In-Reply-To: 3D459394.80104@boosthardware.com

>> Paul Davis wrote:
>>
>> #!/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 ...
>>

I tried the above but it didn't work for me by itself and I don't have 
the insight at the moment to get it to. Thanks anyway because you jogged 
my memory.

I remembered that Jaroslav had given me a command a while ago (last 
year) to get the  module options for each module.

modinfo $(modprobe -l snd-*) | cat > /art/code/alsa/modinfo

This returns a reasonably readable file. If I make a perl script to 
parse that and print a more readable version then I have what I need for 
now.

-- 
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

  reply	other threads:[~2002-07-29 20:25 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
2002-07-29 20:25                         ` Patrick Shirkey [this message]
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=3D45A4A2.5010602@boosthardware.com \
    --to=pshirkey@boosthardware.com \
    --cc=alsa-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox