All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Davis <pbd@Op.Net>
To: pshirkey@boosthardware.com
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Status of ALSA documentation?
Date: Tue, 26 Feb 2002 00:17:01 -0500	[thread overview]
Message-ID: <200202260517.AAA29389@renoir.op.net> (raw)
In-Reply-To: Your message of "Mon, 25 Feb 2002 20:53:20 PST." <20020226045320.EF0EB2755@sitemail.everyone.net>

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

modprobe -n soundcore will test for its existence without doing anything.

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

pointing them at vi will not help such users. just tell them to edit
the file - if they don't know how to do that, this document can't be
of any help to them, really.

>>  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 start
>ed writing a more complete .asoundrc document but haven't finished it yet.

for most people, their most used PCM device will be of type "plug" or
"plughw" (the latter just being a notational convenience rather than
anything truly different).

>>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 w
>orking.

The problem is that these documents will become reference sheets for
each soundcard. Browsing through a couple of pages of install info for
ALSA every time you want to check on that detail about the
CmRMiceCreatEmu Y18kJA card is going to annoy most people. 

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

same deal. i get the page source, it looks OK, but doesn't render.

--p

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

  reply	other threads:[~2002-02-26  5:17 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26  4:53 Status of ALSA documentation? Patrick Shirkey
2002-02-26  5:17 ` Paul Davis [this message]
  -- 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=200202260517.AAA29389@renoir.op.net \
    --to=pbd@op.net \
    --cc=alsa-devel@lists.sourceforge.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.