From: Paul Davis <pbd@Op.Net>
To: Mark Constable <markc@renta.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Status of ALSA documentation?
Date: Fri, 15 Feb 2002 00:03:00 -0500 [thread overview]
Message-ID: <200202150507.AAA05873@renoir.op.net> (raw)
In-Reply-To: Your message of "Fri, 15 Feb 2002 14:56:11 +1000." <E16baPy-0005d8-00@usw-sf-list1.sourceforge.net>
>I recently showed a Mac user interested in using Linux
>for live stage work (no gui needed) the ALSA site so they
>could get some idea of progress... they just laughed and
>said there was _nothing_ there to help them evaluate whether
>ALSA (therefor Linux) was going to be useful to them... well,
>not within a 5 minute perusal anyway.
i think this is an excellent, critical point.
with ALSA's adoption into the kernel, we have both (1) a chance that
more people will write HOWTOs and code but also (2) more people saying
"what is it?" and "how do i ....?" the current web site fails
completely at both tasks.
as much as i think we are still aiming for uniform operation for all
cards (i.e. they just work), i think a good place to start with
interface HOWTOs would be to take Dan's soundcard matrix, and add
links from each card name to a HOWTO. The default set of HOWTOs can be
empty, and we can add to them as time goes on. By empty, what I really
mean is a boilerplate document that says "if you have this type of
soundcard, just do X, Y, and Z and it will work".
there should also be a way to collect card-specific bug reports and
accessing them all from the HOWTO page.
of course a wiki would be an even better way of collecting card/setup
specific quirks, but that seems a bit much to ask for right now.
of course, it becomes critical that the matrix be kept up to date,
which could also use a wiki-style input system.
--p
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next prev parent reply other threads:[~2002-02-15 5:03 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 10:02 Status of ALSA documentation? Patrick Shirkey
2002-02-14 13:57 ` Jaroslav Kysela
2002-02-15 4:56 ` Mark Constable
2002-02-15 5:03 ` Paul Davis [this message]
2002-02-15 7:45 ` Mark Constable
-- strict thread matches above, loose matches on Subject: below --
2002-03-04 8:25 Patrick Shirkey
2002-03-02 23:58 Samuel S Chessman
2002-03-02 19:28 ` Paul Davis
2002-03-02 15:33 Patrick Shirkey
2002-03-02 13:08 Patrick Shirkey
2002-03-02 17:27 ` Paul Davis
2002-03-05 14:56 ` Juhana Sadeharju
2002-03-05 10:18 ` Paul Davis
[not found] <E16g5Uz-0001y7-00@usw-sf-list1.sourceforge.net>
2002-02-28 20:05 ` Juhana Sadeharju
[not found] <E16foSl-0000MV-00@usw-sf-list1.sourceforge.net>
2002-02-28 19:57 ` Juhana Sadeharju
2002-02-27 8:46 Patrick Shirkey
2002-02-27 8:19 Patrick Shirkey
2002-02-27 14:51 ` Paul Davis
2002-02-26 7:20 Patrick Shirkey
2002-02-26 15:10 ` Paul Davis
2002-02-26 7:02 Patrick Shirkey
2002-02-26 15:07 ` Paul Davis
2002-02-26 4:53 Patrick Shirkey
2002-02-26 5:17 ` Paul Davis
2002-02-19 15:01 Patrick Shirkey
2002-02-19 15:42 ` Mark Constable
2002-02-21 6:31 ` Kai Vehmanen
2002-02-25 17:43 ` Paul Davis
2002-02-26 14:49 ` Jaroslav Kysela
2002-02-15 12:12 Patrick Shirkey
2002-02-21 11:31 ` James Tappin
2002-02-15 7:39 Patrick Shirkey
2002-02-15 7:36 Patrick Shirkey
2002-02-15 7:34 Patrick Shirkey
2002-02-15 15:45 ` James Courtier-Dutton
2002-02-15 18:18 ` Kevin Conder
2002-02-15 18:22 ` Paul Davis
2002-02-15 20:23 ` Andy Wingo
2002-02-15 22:05 ` Kevin Conder
2002-02-13 9:32 Patrick Shirkey
2002-02-13 10:05 ` Kai Vehmanen
2002-02-14 9:15 ` Jaroslav Kysela
2002-02-12 16:17 Kevin Conder
2002-02-12 17:17 ` Kai Vehmanen
2002-02-12 18:43 ` Kevin Conder
2002-02-12 19:33 ` Kai Vehmanen
2002-02-12 19:57 ` Jaroslav Kysela
2002-02-13 8:39 ` Guenther Sohler
2002-02-13 9:12 ` Jaroslav Kysela
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=200202150507.AAA05873@renoir.op.net \
--to=pbd@op.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=markc@renta.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.