All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Re: documentation or lack thereof
Date: Wed, 11 Dec 2002 02:59:30 +0900	[thread overview]
Message-ID: <3DF62B82.4070700@boosthardware.com> (raw)
In-Reply-To: E18LQai-0006m2-00@sc8-sf-list1.sourceforge.net

Paul Davis wrote:

> i disagree. there seem to be very few people interested in working on
> alsa-kernel or alsa-lib. most people want a nice, easy to use API so
> that they can dump sounds to an audio interface or possibly record
> them. the number of people with the skills, knowledge and interest in
> working on ALSA has always been remarkably low.
> 
> on the other hand, having more documentation is almost always a good
> thing. now, where are the volunteers?
> 

Lot's of possible flames here but the main thing is that the people who 
do understand the alsa-driver well enough are either too busy to find 
the time or have justifiable reservations about getting their prose online.

Mailing lists are much better for these people than official documents.

Unfortunately the people like myself are not in a position to edit large 
amounts of code documentation which we scour from the lists. I can 
however do a reasonable attempt at formatting the stuff. However I don't 
have much time or inclination to learn docbook at the moment so it 
wouldn't be a standard format.

But it will probably help people if I put the basics up on line. So I 
will do some work on it over the next few days.

AFAIK there is only one other person round here who has the motivation 
and skills to do the docbook work and he must be busy at the moment or 
found other things to do.

Anyway against all odds the past year has netted us the alsa-docs, 
alsa-wiki, Paul and Matthias's basic programming howtos, Takashi's 
desription of how to build a driver which equal 5 new docs. Not bad at all.

The only thing we need now is an indepth doc on doing midi programming 
which Juan Linetsky has started but has declined offering it to the public.


-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

Being on stage with the band in front of crowds shouting, "Get off! No! 
We want normal music!", I think that was more like acting than anything 
I've ever done.

Goldie, 8 Nov, 2002
The Scotsman



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-12-10 17:59 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05 10:47 sb16 gets wedged when doing overlapped i/o (full duplex) John S. Denker
2002-12-05 11:31 ` usbaudio won't do 24-bit or 32-bit i/o, and won't do 96000 frames per second John S. Denker
2002-12-05 15:19   ` Clemens Ladisch
2002-12-05 19:10     ` John S. Denker
2002-12-06  9:16       ` Clemens Ladisch
2002-12-06 10:09         ` Jaroslav Kysela
2002-12-07 15:05           ` Patrick Shirkey
2002-12-06 13:13         ` John S. Denker
2002-12-06 14:22         ` many utils fail for extigy (usb) John S. Denker
2002-12-06  6:48     ` usbaudio won't do 24-bit or 32-bit i/o, and won't do 96000 frames per second Patrick Shirkey
2002-12-06  7:12       ` Patrick Shirkey
2002-12-13 18:19       ` Takashi Iwai
2002-12-14 10:48         ` usbaudio won't do 24-bit or 32-bit i/o Patrick Shirkey
2002-12-16 17:19           ` Takashi Iwai
2002-12-16 18:59             ` Patrick Shirkey
2002-12-16 20:11               ` Patrick Shirkey
2002-12-17 15:28               ` Takashi Iwai
2002-12-20 22:00                 ` Patrick Shirkey
2002-12-23 13:35                   ` Takashi Iwai
2002-12-23 18:58                     ` Patrick Shirkey
2002-12-05 11:39 ` sb16 gets wedged when doing overlapped i/o (full duplex) John S. Denker
2002-12-05 11:52 ` hard crash when snd-ice1712 loads John S. Denker
2002-12-05 17:42   ` Jaroslav Kysela
2002-12-05 23:10   ` Scott Bahling
2002-12-05 11:57 ` alsactl and alsamixer fail for extigy John S. Denker
2002-12-09 14:51   ` Takashi Iwai
2002-12-05 12:07 ` sb16 gets wedged when doing overlapped i/o (full duplex) Uros Bizjak
2002-12-05 13:45   ` John S. Denker
2002-12-05 14:55     ` Uros Bizjak
2002-12-05 17:47       ` Jaroslav Kysela
2002-12-05 18:33       ` John S. Denker
2002-12-06  7:14         ` Uros Bizjak
2002-12-06 14:08           ` John S. Denker
2002-12-06  0:41       ` cs4239 errs on full duplex (provoked by overruns?) John S. Denker
2002-12-05 15:23     ` sb16 gets wedged when doing overlapped i/o (full duplex) Paul Davis
2002-12-09 14:30       ` Takashi Iwai
2002-12-09 14:54     ` documentation or lack thereof John S. Denker
2002-12-09 15:05       ` Takashi Iwai
2002-12-09 15:23       ` ljp
2002-12-09 16:23       ` Paul Davis
2002-12-10 17:59         ` Patrick Shirkey [this message]
2002-12-10 22:28         ` soundcard matrix: broken links etc John S. Denker
2002-12-11  2:52           ` Patrick Shirkey
2002-12-11  4:05         ` John S. Denker
2002-12-11  5:27           ` Patrick Shirkey
2002-12-14 15:59         ` John S. Denker
     [not found] <E18Lut8-0005PF-00@sc8-sf-list2.sourceforge.net>
2002-12-11  5:37 ` Re: documentation or lack thereof Kevin Conder

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=3DF62B82.4070700@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 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.