From: Patrick Shirkey <pshirkey@boosthardware.com>
To: James Tappin <sjt@star.sr.bham.ac.uk>
Cc: ALSA Development <alsa-devel@lists.sourceforge.net>
Subject: Re: new alsa docs.
Date: Tue, 06 Aug 2002 20:12:02 +0900 [thread overview]
Message-ID: <3D4FAF02.7000309@boosthardware.com> (raw)
In-Reply-To: 20020806104713.2f0ce97e.sjt@star.sr.bham.ac.uk
James Tappin wrote:
> On Tue, 06 Aug 2002 18:25:22 +0900
> PS> > On Tue, 06 Aug 2002, Patrick Shirkey wrote:
> PS> >
> PS> >
> PS> >>I'm have soreted out all the final bugs I had with the new docs
> PS> >setup. >Added the midi stuff and I feel that the site is ready for
> PS> >prime time.>
> PS> >>You can see it here:
> PS> >>
> PS> >>http://www.alsa-project.org/alsa-doc/
>
> Just a couple of minor queries.
> 1) In the "Setting up modprobe and kmod support" you do not include the
> line:
> alias sound-service-0-8 snd-seq-oss
> (at least for the two cards relevant to me [trident and ice1712] but you
> do
> include it in the explanation. Which is recommended?
>
Hmmm, good question. I have added it for now as they are different minor
numbers.
> 2) For debian it is possible to add a new file "alsasound" (say) to
> /etc/modutils/ and update-modules will find it (I'm not sure if this is
> recommended practice or not, I'm still very much a beginner with
> debian).
>
Ahh. So all files that configure modules in some way eg startup or
modules.conf are dealt with by modutils? I'll read up and see if I can
make the tip more precise.
> Overall though, a nice piece of work, that should be very useful in
> making ALSA more accessible to new users.
>
Thanks.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-08-06 11:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 15:51 new alsa docs Patrick Shirkey
2002-08-05 20:01 ` Dan Hollis
2002-08-06 9:13 ` Patrick Shirkey
2002-08-06 12:48 ` Joerg Mayer
2002-08-07 7:24 ` Use less number of BDs in i810 Shaju Abraham
2002-08-07 9:54 ` Takashi Iwai
2002-08-06 3:25 ` new alsa docs Andy Wingo
2002-08-06 9:25 ` Patrick Shirkey
2002-08-06 9:47 ` James Tappin
2002-08-06 11:12 ` Patrick Shirkey [this message]
2002-08-07 12:32 ` Takashi Iwai
2002-08-09 19:50 ` Karsten Wiese
2002-08-06 16:24 ` Andy Wingo
2002-08-07 12:27 ` Takashi Iwai
2002-08-07 17:11 ` Niklas Werner
2002-08-08 23:49 ` Scott MacKenzie
2002-08-09 7:19 ` Patrick Shirkey
[not found] <Pine.LNX.4.44.0208061855490.23759-100000@yme.mo.himolde.no>
2002-08-08 15:56 ` Patrick Shirkey
2002-08-09 6:25 ` Antti Boman
2002-08-09 6:52 ` Patrick Shirkey
2002-08-09 7:31 ` Patrick Shirkey
2002-08-10 18:51 ` Frans Ketelaars
2002-08-09 15:27 ` Patrick Shirkey
2002-08-13 14:40 ` Clemens Ladisch
2002-08-13 15:01 ` Patrick Shirkey
2002-08-14 16:01 ` Pedro Lopez-Cabanillas
2002-08-15 8:56 ` Patrick Shirkey
2002-08-15 14:22 ` Pedro Lopez-Cabanillas
2002-08-15 10:19 ` Patrick Shirkey
2002-08-14 16:40 ` Clemens Ladisch
2002-08-15 9:03 ` Patrick Shirkey
2002-08-15 12:25 ` Clemens Ladisch
2002-08-15 12:42 ` Patrick Shirkey
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=3D4FAF02.7000309@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=sjt@star.sr.bham.ac.uk \
/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.