[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080129164237.42ae5251@gaivota>
Date: Tue, 29 Jan 2008 16:42:37 -0200
From: Mauro Carvalho Chehab <mchehab@...radead.org>
To: Trent Piepho <xyzzy@...akeasy.org>
Cc: Adrian Bunk <bunk@...nel.org>, Hans Verkuil <hverkuil@...all.nl>,
v4l-dvb-maintainer@...uxtv.org,
Marcin Slusarz <marcin.slusarz@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [v4l-dvb-maintainer] 2.6.25 regression: VIDEO_DEV=y/m, I2C=n
compile error
Hi Trent,
> Also only the function v4l2_i2c_attach() is a problem. The other functions,
> like v4l2_chip_match_i2c_client(), which the patch put inside an #ifdef
> don't use any i2c symbols and don't need to be protected.
> could even easily be used by a driver that doesn't
> need I2C.
True, but, with the exception of v4l2_chip_match_host(), all the others have
struct i2c_client as an argument. I can't see any valid usage where someone would
fill this struct when i2c is not supported.
---
I'm committing right now a patch that should properly fix the regression. I've
checked it with -git tree and seems to work properly to me.
The Kconfig changes become this way:
diff -r ea8b678dd436 -r 3f704aa9d92e linux/drivers/media/Kconfig
--- a/linux/drivers/media/Kconfig Mon Jan 28 22:11:19 2008 +0000
+++ b/linux/drivers/media/Kconfig Tue Jan 29 16:32:35 2008 -0200
@@ -24,6 +24,11 @@ config VIDEO_DEV
To compile this driver as a module, choose M here: the
module will be called videodev.
+
+config VIDEO_V4L2_COMMON
+ tristate
+ depends on (I2C || I2C=n) && VIDEO_DEV
+ default (I2C || I2C=n) && VIDEO_DEV
The "depends on" clause is equal to default. Probably, it can be safely
removed, but this way seems clearer to my eyes.
Based on my tests, it seems that "depends on" only works fine for values that
are prompted. If the value is not prompted, it just uses whatever declared on
"default".
I'll push the complete changeset to -hg and my -git tree (at devel branch).
Cheers,
Mauro.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists