Skip to contentSkip to conversation

Status of ALSA documentation?

DISCUSSION Patrick Shirkey 2 participants 2 messages Feb 26, 2002

lore
Share & tools
lore
#0 lore raw
Quoted 5 lines · --- Paul Davis
Quoted 5 lines · Patrick Shirkey
Quoted 4 lines

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.

Quoted 7 lines
Quoted 2 lines

[...]

Quoted 1 line

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

Quoted 2 lines

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.

Quoted 1 line

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.

Quoted 5 lines

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.

Quoted 5 lines

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.

Quoted 12 lines

* 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?

Quoted 4 lines
Quoted 1 line
Quoted 1 line

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.

Quoted 5 lines

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.

Quoted 1 line

--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
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

#1 lore raw
Quoted 3 lines

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.

Quoted 2 lines

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.

Quoted 8 lines
Quoted 5 lines

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

Quoted 9 lines
Quoted 5 lines

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.

Quoted 10 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line

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
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel