From: Adrian Bunk <bunk@fs.tum.de>
To: Linus Torvalds <torvalds@osdl.org>,
zippel@linux-m68k.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: GCS <gcs@lsc.hu>, Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.3-rc4
Date: Tue, 17 Feb 2004 21:05:46 +0100 [thread overview]
Message-ID: <20040217200545.GP1308@fs.tum.de> (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 wrote:
>
>
> On Tue, 17 Feb 2004, GCS 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?
>
> 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.
>
> Which implies a configuration error (but the Kconfig file looks correct,
> so I wonder if you found a bug in the configurator).
Most likely the problem is CONFIG_I2C=m and the fact that FB_RADEON_I2C
is a bool.
I don't know whether there's a better way to express this, but something
like the following is required:
--- linux-2.6.3-rc4/drivers/video/Kconfig.old 2004-02-17 21:00:24.000000000 +0100
+++ linux-2.6.3-rc4/drivers/video/Kconfig 2004-02-17 21:01:53.000000000 +0100
@@ -644,7 +644,7 @@
config FB_RADEON_I2C
bool "DDC/I2C for ATI Radeon support"
- depends on FB_RADEON && I2C
+ depends on (FB_RADEON=m && I2C) || (FB_RADEON=y && I2C=y)
select I2C_ALGOBIT
default y
help
> Linus
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-02-17 20:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 3:51 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 [this message]
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
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=20040217200545.GP1308@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=benh@kernel.crashing.org \
--cc=gcs@lsc.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®