All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jordan Breeding <jordan.breeding@attbi.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Linux 2.4.X kernel patches?
Date: Mon, 27 May 2002 11:56:04 +0200	[thread overview]
Message-ID: <s5hu1otewy3.wl@alsa2.suse.de> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAjQHXypTRWUeX0Da3WGxUUMKAAAAQAAAA3uo4sBRfX0CZqrcNroNsggEAAAAA@attbi.com>

At Thu, 23 May 2002 06:48:16 -0000,
Jordan Breeding wrote:
> 
> Hello,
> 
>   Now that alsa is merged in Linux 2.5.x is there any chance that
> patches to add ALSA directly into a Linux 2.4.x kernel will be revived.
> For quite some time now the patches in
> ftp.alsa-project.org/pub/kernel-patches have been 2.5.x only.  I
> understand that 2.5.x is the development kernel but having the option of
> building the latest ALSA drivers directly into a 2.4.x kernel would be
> very nice as well.  Thanks for any information.

i've written (a bit old) 2.4 patches, found at
	ftp://ftp.suse.com/pub/people/tiwai/alsa-2.4-patches

please note that the patch is for suse-modified kernel, so there might
be conflicts with the vanilla kernel (perhaps Configure.help, which
can be ignored or repaired easily.)

since the kernel tree structure was changed on 2.5, the patch is
completely different from 2.5 patch.
my patch will place alsa drivers under linux/drivers/sound/alsa,
while 2.5 tree has the integrated sound directory linux/sound.

i'll update this patch set later in this week again.


Takashi

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

      reply	other threads:[~2002-05-27  9:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-23  6:48 Linux 2.4.X kernel patches? Jordan Breeding
2002-05-27  9:56 ` Takashi Iwai [this message]

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=s5hu1otewy3.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jordan.breeding@attbi.com \
    /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.