From: Takashi Iwai <tiwai@suse.de>
To: Joerg Mayer <jmayer@loplof.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Alsa 0.9 and 2.4 kernel
Date: Mon, 16 Sep 2002 17:03:32 +0200 [thread overview]
Message-ID: <s5hvg56rn7f.wl@alsa2.suse.de> (raw)
In-Reply-To: <20020916164642.A19700@thot.informatik.uni-kl.de>
At Mon, 16 Sep 2002 16:46:42 +0200,
Joerg Mayer wrote:
>
> On Mon, Sep 16, 2002 at 04:41:39PM +0200, Takashi Iwai wrote:
> > > Are there any plans to send alsa 0.9 (or 1.0 or whatever) to Marcelo for
> > > inclusion into the official 2.4 tree?
> >
> > i don't believe that alsa will be intergated into 2.4 line.
> > this will bring too much diffs - the whole bunch of oss tree is
> > moved, if we keep the consistent structure with 2.5.
>
> I agree that oss must not be touched in 2.4, but I see no reason to
> not include it (as an alternative to oss) in the official tree, especially
> as the distribution vendors are adopting it already.
the problem is that 2.5 tree puts oss stuffs on the different location
(linux/sound/oss) than 2.4 has (linux/driver/sound).
thus, we cannot keep the same tree structure between 2.4 and 2.5.
yes, it's possible to put only alsa tree but i don't see big
advantage there.
> > all the current alsa-kernel codes are based on 2.5, and we provide
> > additional wrappers for 2.4. is there any problem in this regard?
>
> I obviously wrote a different question than I intended to ask :-/
> I was wondering about module names, nothing else.
renaming which module, do you mean?
i don't think any sound-related module names have been changed since
2.4.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2002-09-16 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 12:25 Alsa 0.9 and 2.4 kernel Joerg Mayer
2002-09-16 14:41 ` Takashi Iwai
2002-09-16 14:46 ` Joerg Mayer
2002-09-16 15:03 ` 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=s5hvg56rn7f.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=jmayer@loplof.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 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.