From: Joshua Kwan <joshk@triplehelix.org>
To: linux-kernel@vger.kernel.org
Subject: [2.4] bttv and sparc64
Date: Tue, 06 Apr 2004 16:39:44 -0700 [thread overview]
Message-ID: <pan.2004.04.06.23.39.42.565881@triplehelix.org> (raw)
Hi all,
Many modules on sparc64 seem to require I2C support to
compile correctly. Why do they not depend on CONFIG_I2C?
The list of missing symbols is as follows --
depmod: *** Unresolved symbols in ./lib/modules/2.4.25-sparc64/kernel/drivers/media/video/bttv.o
depmod: i2c_bit_add_bus_R73af847e
depmod: i2c_bit_del_bus_R96bec566
depmod: i2c_master_recv_R7bd34477
depmod: virt_to_bus_not_defined_use_pci_map
depmod: i2c_master_send_Rbcec30fe
depmod: *** Unresolved symbols in ./lib/modules/2.4.25-sparc64/kernel/drivers/media/video/msp3400.o
depmod: i2c_detach_client_R13852119
depmod: i2c_attach_client_R29fbc42c
depmod: i2c_add_driver_R64fc78c7
depmod: i2c_probe_Red036271
depmod: i2c_transfer_Rcd9848a7
depmod: i2c_del_driver_Re73c7489
depmod: i2c_master_send_Rbcec30fe
depmod: *** Unresolved symbols in ./lib/modules/2.4.25-sparc64/kernel/drivers/media/video/tda7432.o
depmod: i2c_detach_client_R13852119
depmod: i2c_attach_client_R29fbc42c
depmod: i2c_add_driver_R64fc78c7
depmod: i2c_probe_Red036271
depmod: i2c_del_driver_Re73c7489
depmod: i2c_master_send_Rbcec30fe
depmod: *** Unresolved symbols in ./lib/modules/2.4.25-sparc64/kernel/drivers/media/video/tda9875.o
depmod: i2c_detach_client_R13852119
depmod: i2c_attach_client_R29fbc42c
depmod: i2c_add_driver_R64fc78c7
depmod: i2c_probe_Red036271
depmod: i2c_transfer_Rcd9848a7
depmod: i2c_del_driver_Re73c7489
depmod: i2c_master_send_Rbcec30fe
depmod: *** Unresolved symbols in ./lib/modules/2.4.25-sparc64/kernel/drivers/media/video/tda9887.o
depmod: i2c_detach_client_R13852119
depmod: i2c_attach_client_R29fbc42c
depmod: i2c_add_driver_R64fc78c7
depmod: i2c_probe_Red036271
depmod: i2c_del_driver_Re73c7489
depmod: i2c_master_send_Rbcec30fe
depmod: *** Unresolved symbols in ./lib/modules/2.4.25-sparc64/kernel/drivers/media/video/tuner.o
depmod: i2c_detach_client_R13852119
depmod: i2c_attach_client_R29fbc42c
depmod: i2c_master_recv_R7bd34477
depmod: i2c_add_driver_R64fc78c7
depmod: i2c_probe_Red036271
depmod: i2c_del_driver_Re73c7489
depmod: i2c_master_send_Rbcec30fe
depmod: *** Unresolved symbols in ./lib/modules/2.4.25-sparc64/kernel/drivers/media/video/tvaudio.o
depmod: i2c_detach_client_R13852119
depmod: i2c_attach_client_R29fbc42c
depmod: i2c_master_recv_R7bd34477
depmod: i2c_add_driver_R64fc78c7
depmod: i2c_probe_Red036271
depmod: i2c_transfer_Rcd9848a7
depmod: i2c_del_driver_Re73c7489
depmod: i2c_master_send_Rbcec30fe
depmod: *** Unresolved symbols in ./lib/modules/2.4.25-sparc64/kernel/drivers/usb/w9968cf.o
depmod: i2c_del_adapter_R63923866
depmod: i2c_add_adapter_R04de9506
Any idea what's up? This is 2.4.25 with Debian patches applied (they don't
affect this behavior.)
--
Joshua Kwan
next reply other threads:[~2004-04-06 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 23:39 Joshua Kwan [this message]
2004-04-07 7:12 ` [2.4] bttv and sparc64 Gerd Knorr
2004-04-07 23:52 ` Joshua Kwan
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=pan.2004.04.06.23.39.42.565881@triplehelix.org \
--to=joshk@triplehelix.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).