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: Fri, 26 Sep 2003 11:53:23 +0200 [thread overview]
Message-ID: <s5hbrt7kh9o.wl@alsa2.suse.de> (raw)
In-Reply-To: <NDBBLGIKBJENLAMOLFHGIEOODEAB.mknecht@controlnet.com>
At Thu, 25 Sep 2003 11:27:04 -0700,
Mark Knecht wrote:
>
> > >
> > > 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.
>
> Oops! I thought I was clear up to this, so I want to double, double check.
> When you say 'OSS driver codes' here, you are speaking of the real OSS that
> is not part of Alsa, correct? I have not ever built (TTBOMK) real OSS Sound
> support, and don't want to do so now. I do want 'OSS Emulation' that is
> offered by Alsa. I get this from the Alsa code and not from anything in the
> OSS directory, correct?
right.
* linux/sound/oss = the old good real OSS drivers, which was located
at linux/drivers/sound on 2.4 tree.
(i mean here OSS is not genuine OSS by 4front but
so-called OSS/Free or OSS/Kernel.)
* linux/sound/core/oss = ALSA OSS emulation modules, namely,
snd-pcm-oss and snd-mixer-oss modules.
in addition, in linux/sound directory, you'll find two files which
were originally in linux/drivers/sound on 2.4 kernel: sound_core.c and
sound_firmware.c. since these files are the common base for both ALSA
and OSS, they are put there. and they can be found in alsa-kernel
tree, too, indeed.
> The right answer (in my mind) is that I should be able to delete the oss
> directory in linux/sound, not enable OSS Sound support when I configure the
> kernel, and still get OSS emulation support from Alsa. I hope I have not
> been incorrect about this.
oh, don't remove the contents under linux/sound/oss. since the kernel
configurator needs the files (at least linux/sound/oss/Kconfig), you
should keep them as they are.
> >
> > please remember the difference of alsa-kernel and alsa-driver trees.
> > for 2.6.x kernel, only alsa-kernel tree is used.
>
> Right! The 'drivers' portion of the 2.4 series kernel is now located in
> /linux/sound. I see my hdsp.c driver under pci. If I needed to do an HDSP
> 9652 update, I would take Thomas's work and place it in the
> linux/sound/pci/rme9652 directory and rebuild the kernel and kernel modules.
>
> >
> > 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.
>
> Certainly. Of course, I'm not a programmer, but I cannot understand why and
> end-user like me would want to turn off Alsa support in the kernel but still
> build a driver. I'm trying to be a good citizen. Just give me Alsa and my
> driver and I'll be happy! ;-)
:)
well, if you want to try an experimental driver on 2.6, too, you'll
need build alsa-drivers tree. as long as you need only the drivers
already existing on linux kernel tree, this is not necessary.
HTH.
ciao,
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-09-26 9:53 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
2003-09-25 18:27 ` Mark Knecht
2003-09-26 9:53 ` Takashi Iwai [this message]
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=s5hbrt7kh9o.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.