All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <kotau@firstlinux.net>
To: Paul Davis <pbd@Op.Net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Status of ALSA documentation?
Date: Mon, 25 Feb 2002 20:53:20 -0800 (PST)	[thread overview]
Message-ID: <20020226045320.EF0EB2755@sitemail.everyone.net> (raw)

--- Paul Davis <pbd@Op.Net> wrote:
>>On Tue, 19 Feb 2002, Patrick Shirkey wrote:
>>
>>> I have just uploaded a template for the idea PD had to make a complete
>>> howto for each card and link it to the sound card matrix or something
>>> similar.
>>[...]
>>> http://www.boosthardware.com/LAU/alsa/template2.html
>
>looks OK. a few nitpicks:
>
>  1) don't point people at /lib/modules ... the structure of this
>      tree is different in 2.0, 2.2 and 2.4

Ok I can give the command to load the soundcore module instead. 

eg. modrobe soundcore

>  2) don't put a reference to alsamixer in the template; some cards
>      have no mixer and so it won't do anything useful

I could add that some cards don't use it and provide a link to an amixer howto.

>  3) don't assume that they use vi(1)

Well it is the most popular unix editor. It is just an example for new users who may not even know how to edit a file.

>  4) defining the card name to be of type "hw" might not
>       be too smart for naive "consumer" users who
>       then try to use any old app with that as the PCM
>       device name.
>

This is still fuzzy for me. Should I replace that with "hwshare"? I have started writing a more complete .asoundrc document but haven't finished it yet.

>more generally, it doesn't seem useful to me to duplicate the
>instructions for building+installing+configuring ALSA for each
>card. isn't this what hyperlinks are for? what we need on a per-card
>basis is the stuff thats really specific for that card:
> 

I'm only thinking of LCD. People who may get confused by following links. The easier Linux is for these people the more chance we have of getting hardware working.

> * what modules to load  
> * what module parameters the driver takes
> * a lot of explanation about what they do
> * a list of every Control and PCM switch
> * a lot of explanation about what they do
> * a "FAQ" detailing things like:
>      - how to get sound from the rear speakers?
>      - how to download firmware?
>      - how to get new sounds from the synth?
>      - how to make the synth work?
>      - why do i have to preload module XXX?
>
>>> http://www.boosthardware.com/LAU/alsa/
>
>doesn't render under netscape 4.0
>

You could try.

http://www.boosthardware.com/LAU/alsa/index.html

Otherwise it's windohs or bpftp that are corrupting the files somewhere.

>I think that simply for working on this, Patrick should be made
>webmaster for alsa-project.org. The simple fact that he has bothered
>to do some work on the website moves him beyond almost anybody else on
>the list, though in most cases, for all the right reasons.
>

Sure. At least I have my computers now so can work on things at home. Unfortunately I haven't got net connected yet.

>--p


--
Patrick Shirkey - Boost Hardware Ltd
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/Linux_Audio_Users_Guide/



_____________________________________________________________
Want a new web-based email account ? ---> http://www.firstlinux.net

_____________________________________________________________
You deserve a better email address! Get personalized email @yourname
or @yourcompany from Everyone.net --> http://www.everyone.net?tag

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

             reply	other threads:[~2002-02-26  4:53 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26  4:53 Patrick Shirkey [this message]
2002-02-26  5:17 ` Status of ALSA documentation? Paul Davis
  -- 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-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-14 10:02 Patrick Shirkey
2002-02-14 13:57 ` Jaroslav Kysela
2002-02-15  4:56 ` Mark Constable
2002-02-15  5:03   ` Paul Davis
2002-02-15  7:45     ` Mark Constable
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=20020226045320.EF0EB2755@sitemail.everyone.net \
    --to=kotau@firstlinux.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pbd@Op.Net \
    --cc=pshirkey@boosthardware.com \
    /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.