From: Takashi Iwai <tiwai@suse.de>
To: William <walsac2@liam2.demon.co.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: CVS ALSA failed upgrade in Linux 2.6.3
Date: Tue, 02 Mar 2004 18:33:33 +0100 [thread overview]
Message-ID: <s5hznazm9w2.wl@alsa2.suse.de> (raw)
In-Reply-To: <200403021728.RAA18607@liam2.demon.co.uk>
At Tue, 2 Mar 2004 17:28:18 GMT,
William wrote:
>
> Takashi Iwai <tiwai@suse.de> wrote:
> >> Thanks for explaining that. Please would you delete the word "simply" in
> >> the explanation on alsa-project.org because it's misleading.
> >
> >maybe better to remove the whole sentense.
>
> I think it would be useful to keep an explanation of how to install
> CVS alsa-kernel into a Linux 2.6.x source tree.
>
> BTW, why is there still an alsa-driver package?
> Is there any difference between (a) installing alsa-kernel into Linux 2.6.x
> and (b) installing alsa-driver in the normal way with the configure option
> --with-kernel=somewhere/linux
yes, alsa-kernel is just for update of 2.6.x tree, and it doesn't
include the experimental new drivers included in alsa-driver tree.
alsa-driver tree also includes bunch of wrappers for 2.2/2.4 kernels.
that's why i wrote above to remove the sentense.
if you copy the files of alsa-kernel, you'll have no such new
drivers.
> >the scripts directory shouldn't be copied.
> >also, Documentation directory goes to linux/sound/Documentation/sound/alsa
>
> Don't you mean "linux/sound/Documentation"?
sorry, linux/Documentation/sound/alsa.
Takashi
-------------------------------------------------------
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 17:33 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 [this message]
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
-- 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=s5hznazm9w2.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=walsac2@liam2.demon.co.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.