From: Matt Doran <matt.doran@papercut.com>
To: linux-media@vger.kernel.org
Subject: videodev: Unknown symbol i2c_unregister_device (in kernels older than 2.6.26)
Date: Mon, 25 May 2009 09:10:17 +1000 [thread overview]
Message-ID: <4A19D3D9.9010800@papercut.com> (raw)
Hi there,
I tried using the latest v4l code on an Mythtv box running 2.6.20, but
the v4l videodev module fails to load with the following warnings:
videodev: Unknown symbol i2c_unregister_device
v4l2_common: Unknown symbol v4l2_device_register_subdev
It seems the "i2c_unregister_device" function was added in 2.6.26.
References to this function in v4l2-common.c are enclosed in an ifdef like:
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 26)
However in "v4l2_device_unregister()" in v4l2-device.c, there is a
reference to "i2c_unregister_device" without any ifdefs. I am running
a pretty old kernel, but I'd guess anyone running 2.6.25 or earlier will
have this problem. It seems this code was added by Mauro 3 weeks ago
in this rev:
http://linuxtv.org/hg/v4l-dvb/rev/87afa7a4ccdf
I also had some other compile problems, but don't have all the details
(sorry!). I had to disable the following drivers to get it to compile:
* CONFIG_VIDEO_PVRUSB2
* CONFIG_VIDEO_THS7303
* CONFIG_VIDEO_ADV7343
* CONFIG_DVB_SIANO_SMS1XXX
Regards,
Matt
next reply other threads:[~2009-05-24 23:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 23:10 Matt Doran [this message]
2009-05-25 0:52 ` videodev: Unknown symbol i2c_unregister_device (in kernels older than 2.6.26) David Ward
2009-05-25 1:04 ` Matt Doran
2009-05-25 18:32 ` Andy Walls
2009-05-26 1:42 ` Matt Doran
2009-05-27 18:41 ` Mauro Carvalho Chehab
2009-05-27 18:55 ` [PATCH v2] " Randy Dunlap
2009-06-03 11:51 ` Matt Doran
[not found] ` <4A26637D.1070009@papercut.com>
2009-06-03 12:06 ` 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=4A19D3D9.9010800@papercut.com \
--to=matt.doran@papercut.com \
--cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox