11:54 a.m.
Hi,
linux-2.6-v4l-dvb-update.patch adds a new VIA camera driver
(CONFIG_VIDEO_VIA_CAMERA, disabled in the configuration) which doesn't
build when enabled.
The same patch undeclares I2C_HW_B_RIVA which breaks the build of
rivafb-i2c.o (Which is also disabled in fedora configuration,
CONFIG_FB_RIVA_I2C):
CC [M] drivers/video/riva/rivafb-i2c.o
drivers/video/riva/rivafb-i2c.c: In function 'riva_setup_i2c_bus':
drivers/video/riva/rivafb-i2c.c:97: error: 'I2C_HW_B_RIVA' undeclared
(first use in this function)
drivers/video/riva/rivafb-i2c.c:97: error: (Each undeclared identifier
is reported only once
drivers/video/riva/rivafb-i2c.c:97: error: for each function it appears in.)
Regards,
--
Pardus Linux
http://www.pardus.org.tr/eng
12:35 p.m.
On Dec 22, 2010, at 12:54 PM, Ozan Çağlayan wrote:
Hi,
linux-2.6-v4l-dvb-update.patch adds a new VIA camera driver
(CONFIG_VIDEO_VIA_CAMERA, disabled in the configuration) which doesn't
build when enabled.
Its disabled intentionally, because its known to require newer via
driver bits, only present in 2.6.37, iirc.
The same patch undeclares I2C_HW_B_RIVA which breaks the build of
rivafb-i2c.o (Which is also disabled in fedora configuration,
CONFIG_FB_RIVA_I2C):
CC [M] drivers/video/riva/rivafb-i2c.o
drivers/video/riva/rivafb-i2c.c: In function 'riva_setup_i2c_bus':
drivers/video/riva/rivafb-i2c.c:97: error: 'I2C_HW_B_RIVA' undeclared
(first use in this function)
drivers/video/riva/rivafb-i2c.c:97: error: (Each undeclared identifier
is reported only once
drivers/video/riva/rivafb-i2c.c:97: error: for each function it appears in.)
Probably also requires additional upstream patches. The i2c device
ID stuff has been deprecated for a while, and was removed entirely.
However, I have to ask... Why should we care that something we have
explicitly disabled doesn't build? :)
--
Jarod Wilson
jarod(a)wilsonet.com
12:08 a.m.
Çarşamba 22 Aralık 2010 günü (saat 20:35:48) Jarod Wilson şunları yazmıştı:
On Dec 22, 2010, at 12:54 PM, Ozan Çağlayan wrote:
Probably also requires additional upstream patches. The i2c device
ID stuff has been deprecated for a while, and was removed entirely.
However, I have to ask... Why should we care that something we have
explicitly disabled doesn't build? :)
No problem. I'm taking a lot of Fedora patches to my tree and because the
configuration differs in some places, I've noticed those failures and just
wanted to tell.
Regards,
---
Ozan Çağlayan
TUBITAK/UEKAE - Pardus Linux
http://www.pardus.org.tr/eng
12:43 p.m.
On Wed, Dec 22, 2010 at 07:54:40PM +0200, Ozan Çağlayan wrote:
The same patch undeclares I2C_HW_B_RIVA which breaks the build of
rivafb-i2c.o (Which is also disabled in fedora configuration,
CONFIG_FB_RIVA_I2C):
CC [M] drivers/video/riva/rivafb-i2c.o
drivers/video/riva/rivafb-i2c.c: In function 'riva_setup_i2c_bus':
drivers/video/riva/rivafb-i2c.c:97: error: 'I2C_HW_B_RIVA' undeclared
(first use in this function)
drivers/video/riva/rivafb-i2c.c:97: error: (Each undeclared identifier
is reported only once
drivers/video/riva/rivafb-i2c.c:97: error: for each function it appears in.)
Why would you want to use rivafb? nouveau drives pretty much everything
relevant that rivafb supports.
--
Matthew Garrett | mjg59(a)srcf.ucam.org
4874
days inactive
4875
days old
kernel@lists.fedoraproject.org
3 comments
3 participants
participants (3)
-
Jarod Wilson -
Matthew Garrett -
Ozan Çağlayan