RE: SOLVED = RE: Alsa & 2.6 kernel

["Mark Knecht" <mknecht@controlnet.com>]

Takashi-san,
   Thanks very much. It's making more sense.

   A couple of questions are embedded below. I think you only need to answer
then if you think I'm confused which is a definite possibility. ;-)

> >
> >    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?

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.

>
> 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! ;-)

>
> 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.

Way beyond me, I think, but thanks for the info. Maybe it will sink in
later.

Cheers,
Mark




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