Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: William <walsac2@liam2.demon.co.uk>
To: tiwai@suse.de
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: CVS ALSA failed upgrade in Linux 2.6.3
Date: Tue, 2 Mar 2004 15:52:24 GMT	[thread overview]
Message-ID: <200403021552.PAA17739@liam2.demon.co.uk> (raw)
In-Reply-To: <s5h3c8rfeg8.wl@alsa2.suse.de>

Takashi Iwai <tiwai@suse.de> wrote:
>>William wrote:
>> Jaroslav wrote on alsa-project.org:
>> 
>>    "simply copy files from the ALSA's alsa-kernel CVS module to relevant
>>    locations in the 2.6 kernel tree."
>> 
>> This is one method of upgrading to CVS ALSA.
>
>"simply copy" doesn't mean so simply copy :)

Thanks for explaining that.  Please would you delete the word "simply" in
the explanation on alsa-project.org because it's misleading.

>for example, alsa-kernel/include directory goes to
>linux/include/sound.

Ok, so is my summary below correct?

   $ cp -fR alsa-kernel/include/*  linux/include/sound
   $ mv -f alsa-kernel/include  out-of-the-way-temporarily
   $ cp -fR alsa-kernel/*  linux/sound

> also, it might be safer to leave oss things.

What do you mean "might be safer"?  That it's really necessary to leave oss?
Or that you're not certain?

>if you're not sure, just build alsa-driver with 2.6 kernels as well as
>you did for 2.4 kernels.  it should be ok now.

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

  reply	other threads:[~2004-03-02 15:52 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 [this message]
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
  -- 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=200403021552.PAA17739@liam2.demon.co.uk \
    --to=walsac2@liam2.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tiwai@suse.de \
    /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