From: William <walsac2@liam2.demon.co.uk>
To: James@superbug.demon.co.uk
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: CVS ALSA failed upgrade in Linux 2.6.3
Date: Wed, 3 Mar 2004 15:54:24 GMT [thread overview]
Message-ID: <200403031554.PAA07108@liam2.demon.co.uk> (raw)
In-Reply-To: <40452FE3.8080202@superbug.demon.co.uk>
James Courtier-Dutton <James@superbug.demon.co.uk> wrote:
>
>The point of option 1 is to explain how to upgrade alsa if you need to.
>Not everyone needs to upgrade.
My point was that the explanation given in option is actually confusing.
I guess it's the wiki problem of many different people collaboratively
editing a wiki page, leading to incoherency. That wiki page would probably
benefit from having just one person rewrite it from scratch.
>If you wish to use the cvs, you have to get alsa-driver and alsa-kernel,
>because alsa-driver uses files from ../alsa-kernel
Yes, I knew that already but what I didn't know was that it is best
to install alsa-driver not alsa-kernel to get all the new/experimental drivers.
>So, if you follow the cvs command exactly it will work.
It didn't work (Unknown symbols in snd*) but at least I know why (Takashi said
the CVS alsa-driver is currently in the middle of a major rewrite).
Thanks anyway.
William
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-03-03 15:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 15:20 CVS ALSA failed upgrade in Linux 2.6.3 William
2004-03-02 15:36 ` Takashi Iwai
2004-03-02 15:52 ` William
2004-03-02 16:39 ` Takashi Iwai
2004-03-02 17:28 ` William
2004-03-02 17:33 ` Takashi Iwai
2004-03-02 17:59 ` William
2004-03-02 18:04 ` Takashi Iwai
2004-03-03 14:50 ` William
2004-03-02 21:08 ` James Courtier-Dutton
2004-03-02 23:35 ` William
2004-03-03 1:07 ` James Courtier-Dutton
2004-03-03 15:54 ` William [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-23 9:18 [PATCH] add aplaymidi & arecordmidi utils Clemens Ladisch
2004-02-23 9:41 ` Jaroslav Kysela
2004-02-24 17:12 ` Will
2004-02-24 17:36 ` Clemens Ladisch
2004-02-24 17:51 ` Will
2004-02-24 17:58 ` Clemens Ladisch
2004-02-25 0:10 ` Will
2004-02-25 8:23 ` Clemens Ladisch
2004-02-25 13:22 ` Will
2004-02-25 13:58 ` James Courtier-Dutton
2004-02-25 14:11 ` Will
2004-02-24 17:26 ` Will
2004-02-24 17:43 ` Clemens Ladisch
2004-02-25 13:02 ` Will
2004-02-25 14:04 ` Takashi Iwai
2004-02-25 14:19 ` Will
2004-02-25 14:26 ` Takashi Iwai
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=200403031554.PAA07108@liam2.demon.co.uk \
--to=walsac2@liam2.demon.co.uk \
--cc=James@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox