All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Knecht <mknecht@controlnet.com>
Cc: Alsa-Devel <Alsa-Devel@lists.sourceforge.net>
Subject: Re: SOLVED = RE: Alsa & 2.6 kernel
Date: Thu, 25 Sep 2003 19:11:11 +0200	[thread overview]
Message-ID: <s5hhe30kd3k.wl@alsa2.suse.de> (raw)
In-Reply-To: <NDBBLGIKBJENLAMOLFHGEEOFDEAB.mknecht@controlnet.com>

At Thu, 25 Sep 2003 07:45:08 -0700,
Mark Knecht wrote:
> 
> > At Wed, 24 Sep 2003 14:24:29 -0700,
> > Mark Knecht wrote:
> > >
> > > I see that in the Gentoo kernel tree (and maybe all 2.6 kernels)
> > > linux/drivers/sound has moved to linux/sound.
> >
> > the OSS drivers are located now on linux/sound/oss.
> > the other sound directories correspond to ALSA's alsa-kernel tree
> > (except for alsa-kernel/include -> linux/include/sound, and
> >  alsa-kernel/Documentation -> linux/Documentation/sound/alsa).
> >
> >
> > Takashi
> >
> 
> Takashi-san,
>    Thank you very much for the response. It is helpful.
> 
>    Would I be correct that if I had a 2.6 level kernel and wanted to use the
> newest Alsa from CVS, then I would:
> 
> 1) Download CVS to my machine in it's own directory
> 2) Replace what is currently in linux/sound with the CVS source EXCEPT for
> the oss directory which I would leave alone.
> 3) Build the kernel with Alsa sound support and no OSS support
> 4) Use Alsa to do OSS emulation like I do today in modules.conf
> 
>    In linux/sound there are a few other files - Kconfig, etc. If these are
> not supplied by Alsa CVS, then I would leave them in linux/sound to perform
> whatever function they perform today.
> 
>    Does this sound about right? I may try it out one of these days.

yes.  alsa-kernel tree includes the all files (including Kconfig)
except for OSS driver codes under oss directory.

please remember the difference of alsa-kernel and alsa-driver trees.
for 2.6.x kernel, only alsa-kernel tree is used.

also, you can build on alsa-drivers as well as 2.4.x (i fixed this
yesterday).  but in this case, note that the kernel configuration will
override the local configuration of alsa-driver (provided by configure
script).
for example, if you turn off the ALSA support on 2.6.x kernel config,
you cannot build on alsa-drivers tree properly at all.
this causes often problems when CONFIG_SND_DEBUG mismatches between
kernel and alsa-driver trees.

also, when the kernel is compiled with MODVERSION, you'll have many
compile warnings on alsa-driver tree, due to redefinition of symbols.
but you can ignore them in general.


ciao,

Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2003-09-25 17:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 17:50 Alsa & 2.6 kernel Mark Knecht
2003-09-24 21:24 ` SOLVED = " Mark Knecht
2003-09-25  9:13   ` Takashi Iwai
2003-09-25 14:45     ` Mark Knecht
2003-09-25 17:11       ` Takashi Iwai [this message]
2003-09-25 18:27         ` Mark Knecht
2003-09-26  9:53           ` Takashi Iwai
2003-09-26 14:50             ` Mark Knecht

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=s5hhe30kd3k.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=Alsa-Devel@lists.sourceforge.net \
    --cc=mknecht@controlnet.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.