From: "Andreas Herrmann" <andreas.herrmann3@amd.com>
To: "Mauro Carvalho Chehab" <mchehab@infradead.org>
Cc: "Roman Zippel" <zippel@linux-m68k.org>,
"Oliver Neukum" <oneukum@suse.de>,
linux-usb-devel@lists.sourceforge.net,
video4linux-list@redhat.com,
"Toralf Förster" <toralf.foerster@gmx.de>,
luca.risolia@studio.unibo.it,
"Jan Engelhardt" <jengelh@linux01.gwdg.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c
Date: Fri, 22 Jun 2007 15:46:05 +0200 [thread overview]
Message-ID: <20070622134605.GN5193@alberich.amd.com> (raw)
In-Reply-To: <1182518566.14289.20.camel@gaivota>
On Fri, Jun 22, 2007 at 10:22:46AM -0300, Mauro Carvalho Chehab wrote:
> Hi Roman,
>
> Several instabilities on Kconfig started to happen after replacing
> Kconfig menus to use menuconfig, as this one, reported by Oliver:
>
> Em Qui, 2007-06-21 às 13:50 +0200, Oliver Neukum escreveu:
> > Am Donnerstag, 21. Juni 2007 schrieb Toralf Förster:
> > > Right, but IMHO this issue is typical for a problem with the Kconfig definitions of this module.
> > >
> > > I'll set USB devs as Cc: therefore.
> >
> > The Kconfig there is incomplete.
> > Mauro, please apply.
> >
> > Regards
> > Oliver
> > Signed-off-by: Oliver Neukum <oneukum@suse.de>
> >
> > --- a/drivers/media/video/zc0301/Kconfig 2007-06-21 13:44:14.000000000 +0200
> > +++ b/drivers/media/video/zc0301/Kconfig 2007-06-21 13:44:33.000000000 +0200
> > @@ -1,6 +1,6 @@
> > config USB_ZC0301
> > tristate "USB ZC0301[P] Image Processor and Control Chip support"
> > - depends on VIDEO_V4L1
> > + depends on VIDEO_V4L1 && USB
> > ---help---
> > Say Y here if you want support for cameras based on the ZC0301 or
> > ZC0301P Image Processors and Control Chips.
> >
>
> In this specific case, all V4L USB drivers depends on V4L_USB_DRIVERS,
> that depends, in turn, on USB. So, if USB is not selected,
> V4L_USB_DRIVERS should be unselected, unselecting zc0301.
>
> Unfortunately, the Kernel building system is not properly handling it.
>
> This is the (snipped) media/video/Kconfig:
>
> menuconfig V4L_USB_DRIVERS
> bool "V4L USB devices"
> depends on USB
> default y
>
> if V4L_USB_DRIVERS
>
> source "drivers/media/video/pvrusb2/Kconfig"
>
> <snip/>
>
> source "drivers/media/video/zc0301/Kconfig"
>
> <snip/>
>
> endif # V4L_USB_DRIVERS
>
> --
> Cheers,
> Mauro
>
Hi,
I am not sure whether it is related or not
But if you select USB as module but build your v4l_usb driver
into the kernel you also get compile errors.
Attached is a patch which will prevent this by changing the menuconfig
from bool to tristate.
Regards,
Andreas
--
Correct Kconfig to avoid compile errors like
drivers/built-in.o: In function `sn9c102_usb_disconnect':
sn9c102_core.c:(.text+0x8d840): undefined reference to `usb_get_dev'
Signed-off-by: Andreas Herrmann <andreas.herrmann3@amd.com>
diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
index 4cca551..4754d98 100644
--- a/drivers/media/video/Kconfig
+++ b/drivers/media/video/Kconfig
@@ -687,7 +687,7 @@ config VIDEO_CAFE_CCIC
#
menuconfig V4L_USB_DRIVERS
- bool "V4L USB devices"
+ tristate "V4L USB devices"
depends on USB
default y
next prev parent reply other threads:[~2007-06-22 13:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200706211117.55908.toralf.foerster@gmx.de>
[not found] ` <200706211231.53898.luca.risolia@studio.unibo.it>
[not found] ` <200706211326.45031.toralf.foerster@gmx.de>
[not found] ` <200706211350.14526.oneukum@suse.de>
2007-06-22 13:22 ` Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c Mauro Carvalho Chehab
2007-06-22 13:46 ` Andreas Herrmann [this message]
2007-06-22 13:51 ` Jan Engelhardt
2007-06-22 14:23 ` Andreas Herrmann
2007-06-22 15:03 ` Mauro Carvalho Chehab
2007-06-22 15:32 ` Andreas Herrmann
2007-06-22 15:45 ` Oliver Neukum
2007-06-22 14:27 ` Roman Zippel
2007-06-22 15:18 ` Jan Engelhardt
2007-06-22 16:24 ` Roman Zippel
2007-06-22 16:42 ` Jan Engelhardt
2007-06-22 20:17 ` Satyam Sharma
2007-06-22 21:00 ` Satyam Sharma
2007-06-22 15:21 ` Mauro Carvalho Chehab
2007-06-22 16:31 ` Roman Zippel
2007-06-22 20:20 ` Trent Piepho
2007-06-22 21:20 ` Satyam Sharma
2007-06-22 21:45 ` Roman Zippel
2007-06-22 22:01 ` Satyam Sharma
2007-06-22 22:21 ` Roman Zippel
2007-06-22 22:33 ` Satyam Sharma
2007-06-22 23:12 ` Roman Zippel
2007-06-22 23:26 ` Satyam Sharma
2007-06-22 23:39 ` Roman Zippel
2007-06-22 23:49 ` Satyam Sharma
2007-06-23 0:26 ` Roman Zippel
2007-06-23 6:57 ` Jan Engelhardt
2007-06-25 0:11 ` Roman Zippel
2007-06-22 22:11 ` Jan Engelhardt
2007-06-23 12:28 ` Kconfig troubles when using menuconfig - Was: [patch]Re: " Oleg Verych
2007-06-23 22:33 ` Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] " Trent Piepho
2007-06-24 3:28 ` Satyam Sharma
2007-06-23 7:20 ` [patch] 2.6.22-rc Kconfig troubles when using menuconfig Jan Engelhardt
2007-06-23 22:26 ` Mauro Carvalho Chehab
2007-06-24 0:14 ` Trent Piepho
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=20070622134605.GN5193@alberich.amd.com \
--to=andreas.herrmann3@amd.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=luca.risolia@studio.unibo.it \
--cc=mchehab@infradead.org \
--cc=oneukum@suse.de \
--cc=toralf.foerster@gmx.de \
--cc=video4linux-list@redhat.com \
--cc=zippel@linux-m68k.org \
/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.