From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Shirkey Subject: Re: Status of ALSA documentation? Date: Thu, 14 Feb 2002 23:34:47 -0800 (PST) Message-ID: <20020215073447.98ACB274E@sitemail.everyone.net> Reply-To: pshirkey@boosthardware.com Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-Disposition: inline Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Paul Davis Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org --- Paul Davis wrote: >>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. > Very good idea. The alsa-howto can easliy be linked to in this regard. Just needs a slight formatting change and a lot of tedious typing but give me a couple of months and it should be out of the way. >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. > I suggest updating it once every month. Once the bulk is done it should only take about a small amount of work to add new cards. Mostly just copy and paste. >--p > >_______________________________________________ >Alsa-devel mailing list >Alsa-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/alsa-devel _____________________________________________________________ Want a new web-based email account ? ---> http://www.firstlinux.net _______________________________________________ Alsa-devel mailing list Alsa-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-devel