From: Michael Krufky <mkrufky@linuxtv.org>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-kernel@vger.kernel.org, v4l-dvb-maintainer@linuxtv.org,
video4linux-list@redhat.com
Subject: Re: [v4l-dvb-maintainer] build #340 failed for 2.6.24-rc5-g75b8c13 in linux/drivers/media/video/tuner.ko
Date: Wed, 12 Dec 2007 08:42:43 -0500 [thread overview]
Message-ID: <475FE553.4020702@linuxtv.org> (raw)
In-Reply-To: <200712120934.46156.toralf.foerster@gmx.de>
Toralf Förster wrote:
> Hello,
>
> the build with the attached .config failed, make ends with:
> ...
> GZIP arch/x86/boot/compressed/vmlinux.bin.gz
> LD arch/x86/boot/compressed/piggy.o
> LD arch/x86/boot/compressed/vmlinux
> OBJCOPY arch/x86/boot/vmlinux.bin
> HOSTCC arch/x86/boot/tools/build
> BUILD arch/x86/boot/bzImage
> Root device is (3, 8)
> Setup is 11320 bytes (padded to 11776 bytes).
> System is 1848 kB
> Kernel: arch/x86/boot/bzImage is ready (#1)
> Building modules, stage 2.
> MODPOST 352 modules
> ERROR: "tea5761_attach" [drivers/media/video/tuner.ko] undefined!
> ERROR: "tea5761_autodetection" [drivers/media/video/tuner.ko] undefined!
> ERROR: "tea5767_autodetection" [drivers/media/video/tuner.ko] undefined!
> ERROR: "tea5767_attach" [drivers/media/video/tuner.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
>
> The build was made with an old .config from kernel 2.6.24-rc2
> (where the build also failed) :
> $> make mrproper && cp <oldconfig> .config && make oldconfig && make
>
> Here's the config:
>
> [snip]
>
> CONFIG_VIDEO_TUNER=m
> CONFIG_VIDEO_TUNER_CUSTOMIZE=y
> # CONFIG_TUNER_MT20XX is not set
> CONFIG_TUNER_TDA8290=m
> CONFIG_TUNER_TEA5761=y
> CONFIG_TUNER_TEA5767=y
> CONFIG_TUNER_SIMPLE=m
>
Toralf,
It looks like the problem has something to do with VIDEO_TUNER=m while
both TUNER_TEA5761 & TUNER_TEA5767 are set to 'y'.
I thought that we had already seen this issue and fixed it, but I guess
not :-/
One would think that this could be fixed by making TUNER_TEA5761 &
TUNER_TEA5767 both depend on VIDEO_TUNER , but that would be wrong,
since each of those modules can be attached directly to a bridge driver
without tuner.ko being present at all (although this is not done in
practice right now, but it *is* the case with some other tuner drivers)
I'm going to have to think about this for a bit and do some
experimentation. Thanks for reporting.
Regards,
Mike
next prev parent reply other threads:[~2007-12-12 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 8:34 build #340 failed for 2.6.24-rc5-g75b8c13 in linux/drivers/media/video/tuner.ko Toralf Förster
2007-12-12 13:42 ` Michael Krufky [this message]
2007-12-12 14:46 ` [v4l-dvb-maintainer] " Mauro Carvalho Chehab
2007-12-12 16:00 ` mkrufky
2007-12-12 17:57 ` [v4l-dvb-maintainer] build #340 failed for 2.6.24-rc5-g75b8c13 in?linux/drivers/media/video/tuner.ko Adrian Bunk
2007-12-13 20:11 ` Mauro Carvalho Chehab
2007-12-12 18:40 ` [2.6 patch] drivers/media/Makefile: always enter video/ Adrian Bunk
2007-12-12 21:13 ` [v4l-dvb-maintainer] " Trent Piepho
2007-12-12 21:16 ` [v4l-dvb-maintainer] [2.6 patch] drivers/media/Makefile: alwa ys " mkrufky
2007-12-13 9:55 ` [v4l-dvb-maintainer] [2.6 patch] drivers/media/Makefile: always " Mauro Carvalho Chehab
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=475FE553.4020702@linuxtv.org \
--to=mkrufky@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=video4linux-list@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox