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: Tue, 2 Mar 2004 23:35:17 GMT [thread overview]
Message-ID: <200403022335.AAA22545@liam2.demon.co.uk> (raw)
In-Reply-To: <4044F7B0.3000305@superbug.demon.co.uk>
James Courtier-Dutton <James@superbug.demon.co.uk> wrote:
>
>Use directions at: -
>http://alsa.opensrc.org/index.php?page=AlsaBuild2.6
>
Thanks, James. Like I said in my previous reply to you, the section
describing option 1 is confusing because it seems to contradict itself
firstly by saying alsa-driver is needed (at the first paragraph) and
secondly by saying alsa-driver might not be needed (at the end of the section)
because Linux 2.6.3 includes alsa-driver-1.0.2,
which misses the point of wanting to use CVS alsa-driver in the first place,
i.e. to get the very latest drivers -- not those in alsa-driver-1.0.2.
Basically it doesn't explain why you should install CVS alsa-drivers.
Also it doesn't say what to do with alsa-kernel yet the cvs example shows
alsa-kernel being checked out. As Takashi Iwai said earlier, alsa-kernel
includes stable drivers only and excludes new/experimental drivers.
My understanding is you should install either alsa-kernel or CVS alsa-drivers,
but not both of them.
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-02 23:35 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 [this message]
2004-03-03 1:07 ` James Courtier-Dutton
2004-03-03 15:54 ` William
-- 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=200403022335.AAA22545@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 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.