At Tue, 16 Dec 2008 21:12:58 +0200,Ozan Çağlayan wrote:> > Hi,> > Yesterday I was trying to compile the latest snapshot of alsa-driver on > top of kernel 2.6.28_rc8. When looking through the console output of > make, I saw two warnings given by LD reporting two unknown symbols in > snd-fm801.ko(driver for a ForteMedia sound card):> > Building modules, stage 2.> MODPOST 170 modules> WARNING: "snd_tea575x_init" > [/var/pisi/alsa-driver-1.0.18a_20081214-39/work/alsa-driver/pci/snd-fm801.ko] > undefined!> WARNING: "snd_tea575x_exit" > [/var/pisi/alsa-driver-1.0.18a_20081214-39/work/alsa-driver/pci/snd-fm801.ko] > undefined!> > laptop alsa-driver # grep -rHIn "snd_tea575x_init" *> alsa-kernel/i2c/other/tea575x-tuner.c:195:void snd_tea575x_init(struct snd_tea575x *tea)> alsa-kernel/i2c/other/tea575x-tuner.c:251:EXPORT_SYMBOL(snd_tea575x_init);> alsa-kernel/include/tea575x-tuner.h:51:void snd_tea575x_init(struct snd_tea575x *tea);> alsa-kernel/pci/fm801.c:1447: snd_tea575x_init(&chip->tea);> i2c/other/tea575x-tuner.c:236:void snd_tea575x_init(struct snd_tea575x *tea)> i2c/other/tea575x-tuner.c:309:EXPORT_SYMBOL(snd_tea575x_init);> include/sound/tea575x-tuner.h:51:void snd_tea575x_init(struct snd_tea575x *tea);> pci/fm801.c:1448: snd_tea575x_init(&chip->tea);> pci/fm801.c.orig:1447: snd_tea575x_init(&chip->tea);> sound/i2c/other/tea575x-tuner.c:195:void snd_tea575x_init(struct snd_tea575x *tea)> sound/i2c/other/tea575x-tuner.c:251:EXPORT_SYMBOL(snd_tea575x_init);> sound/include/tea575x-tuner.h:51:void snd_tea575x_init(struct snd_tea575x *tea);> sound/pci/fm801.c:1447: snd_tea575x_init(&chip->tea);> > So this symbols are exported by tea575x-tuner.c. There's a card option parameter> in configuration of alsa-driver called 'fm801-tea575x-bool'.But eventhough, I'm configuring> the package with, "--with-card-options=all", I'm getting this warnings. As a consequence> it's impossible to load the module snd-fm801.> > I think that it's a problem with Kconfig stuff but I really don't get how alsa-driver package> manages the whole thing with alsa-kernel directory, patchsets etc.(BTW, is there any documentation about> the mechanism in alsa-driver, and the functions of separate git repos alsa-driver, alsa-kernel, stub, etc.?)> > I'm having the issue with> 2.6.25.x && (1.0.17 || 1.0.18),> 2.6.28_rc8 && (1.0.18)> > so the problem may not be caught until this time because there exists a few distributions which ships> alsa-driver(and other kernel modules) separately. I guess it has to do with your kernel config.Please attach it. Takashi_______________________________________________Alsa-devel mailing listAlsa-devel@xxxxxxxxxxxxxxxxxxxx://mailman.alsa-project.org/mailman/listinfo/alsa-devel
