From: GCS <gcs@lsc.hu>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.3-rc4
Date: Wed, 18 Feb 2004 01:21:27 +0100 [thread overview]
Message-ID: <20040218002127.GA27422@lsc.hu> (raw)
In-Reply-To: <Pine.LNX.4.58.0402171107040.2154@home.osdl.org>
On Tue, Feb 17, 2004 at 11:09:45AM -0800, Linus Torvalds <torvalds@osdl.org> wrote:
> > drivers/built-in.o(.text+0xb2c44): In function `radeon_do_probe_i2c_edid':
> > : undefined reference to `i2c_transfer'
> > make: *** [.tmp_vmlinux1] Error 1
> >
> > .config snippshet:
> > # CONFIG_FB_RADEON_OLD is not set
> > CONFIG_FB_RADEON=y
> > CONFIG_FB_RADEON_I2C=y
> > CONFIG_FB_RADEON_DEBUG=y
>
> I don't see this. What's your I2C config, and how did you generate your
> config file?
I do not attach it, as I think I have found the root of the problem.
Usually I save my .config to a safe place, copy it into the kernel
source, do 'make oldconfig', and only if necessary I do 'make menuconfig'
as well.
> CONFIG_FB_RADEON_I2C should depend on CONFIG_I2C, and it selects
> I2C_ALGOBIT, but your error messages seem to imply that you don't have i2c
> enabled at all.
I have. My shot would be that as CONFIG_FB_RADEON_I2C is y-n, but
CONFIG_I2C and CONFIG_I2C_ALGOBIT are tri-state as m in my case, the
problem can be that the functions are compiled into the module and
CONFIG_FB_RADEON_I2C can't find them in the static part of the kernel.
At least I do confirm that changing CONFIG_I2C and CONFIG_I2C_ALGOBIT
from m to y makes the problem disappear.
> Which implies a configuration error (but the Kconfig file looks correct,
> so I wonder if you found a bug in the configurator).
Can the configurator force the dependencies to the same state? For my
case it should have change my m's to y's.
Cheers,
GCS
next prev parent reply other threads:[~2004-02-18 0:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 3:51 Linux 2.6.3-rc4 Linus Torvalds
2004-02-17 6:19 ` Felix Seeger
2004-02-17 8:54 ` Martin Diehl
2004-02-17 9:27 ` Martin Diehl
2004-02-17 15:39 ` Bartlomiej Zolnierkiewicz
2004-02-17 16:21 ` Linux 2.6.3-rc4 (compile stats) John Cherry
2004-02-17 18:45 ` Linux 2.6.3-rc4 GCS
2004-02-17 19:09 ` Linus Torvalds
2004-02-17 20:05 ` Adrian Bunk
2004-02-17 20:16 ` Linus Torvalds
2004-02-17 22:59 ` Adrian Bunk
2004-02-17 23:11 ` Linus Torvalds
2004-02-17 23:37 ` Radeon issue on x86 Benjamin Herrenschmidt
2004-02-18 0:17 ` Linus Torvalds
2004-02-18 0:33 ` Benjamin Herrenschmidt
2004-02-18 0:00 ` Linux 2.6.3-rc4 Adrian Bunk
2004-02-18 1:28 ` Roman Zippel
2004-02-18 0:39 ` Roman Zippel
2004-02-18 1:06 ` Roman Zippel
2004-02-18 2:45 ` Roman Zippel
2004-02-18 2:58 ` Linus Torvalds
2004-02-18 0:15 ` Roman Zippel
2004-02-18 0:21 ` GCS [this message]
2004-02-17 18:56 ` Jonathan Brown
2004-02-17 19:06 ` Linus Torvalds
2004-02-18 10:18 ` Andreas Happe
2004-02-18 4:06 ` Stephen Rothwell
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=20040218002127.GA27422@lsc.hu \
--to=gcs@lsc.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.