public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org,
	"Antonino A. Daplas" <adaplas@hotpop.com>
Subject: [patch] Re: 2.6.7-mm1 linker trouble with CONFIG_FB_RIVA_I2C=y and modular I2C
Date: Mon, 21 Jun 2004 17:29:06 +0200	[thread overview]
Message-ID: <20040621152905.GC28607@fs.tum.de> (raw)
In-Reply-To: <20040621020627.GA10824@merlin.emma.line.org>

On Mon, Jun 21, 2004 at 04:06:27AM +0200, Matthias Andree wrote:
> On Sun, 20 Jun 2004, Andrew Morton wrote:
> 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7/2.6.7-mm1/
> 
> This version causes linker trouble with
> CONFIG_I2C=m
> CONFIG_I2C_ALGOBIT=m
> CONFIG_FB_RIVA_I2C=y
> 
>   CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> drivers/built-in.o(.text+0xda101): In function `riva_setup_i2c_bus':
> : undefined reference to `i2c_bit_add_bus'
> drivers/built-in.o(.text+0xda218): In function `riva_delete_i2c_busses':
> : undefined reference to `i2c_bit_del_bus'
> drivers/built-in.o(.text+0xda237): In function `riva_delete_i2c_busses':
> : undefined reference to `i2c_bit_del_bus'
> drivers/built-in.o(.text+0xda2c9): In function `riva_do_probe_i2c_edid':
> : undefined reference to `i2c_transfer'
> make: *** [.tmp_vmlinux1] Error 1
>...

Thanks for this report.

The problem is:
FB_RIVA=y
FB_RIVA_I2C=y
I2C=m
I2C_ALGOBIT=m

The patch below fixes this.

Besides this, it contains:
- help text by Antonino A. Daplas
- converted spaces to tabs
- it was forgotten that FB_RIVA_I2C requires I2C_ALGOBIT

> Matthias Andree

cu
Adrian

--- linux-2.6.7-mm1-modular/drivers/video/Kconfig.old	2004-06-21 17:09:57.000000000 +0200
+++ linux-2.6.7-mm1-modular/drivers/video/Kconfig	2004-06-21 17:26:57.000000000 +0200
@@ -424,6 +424,8 @@
 config FB_RIVA
 	tristate "nVidia Riva support"
 	depends on FB && PCI
+	select I2C_ALGOBIT if FB_RIVA_I2C
+	select I2C if FB_RIVA_I2C
 	help
 	  This driver supports graphics boards with the nVidia Riva/Geforce
 	  chips.
@@ -433,9 +435,17 @@
 	  module will be called rivafb.
 
 config FB_RIVA_I2C
-       bool "Enable DDC Support"
-       depends on FB_RIVA && I2C
-       help
+	bool "Enable DDC Support"
+	depends on FB_RIVA
+	help
+	  This enables I2C support for nVidia Chipsets.  This is used
+	  only for getting EDID information from the attached display
+	  allowing for robust video mode handling and switching.
+
+	  Because fbdev-2.6 requires that drivers must be able to
+	  independently validate video mode parameters, you should say Y
+	  here.
+
 
 config FB_I810
 	tristate "Intel 810/815 support (EXPERIMENTAL)"

  reply	other threads:[~2004-06-21 15:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21  0:46 2.6.7-mm1 Andrew Morton
2004-06-21  1:40 ` 2.6.7-mm1: empty help text for FB_RIVA_I2C Adrian Bunk
2004-06-21  7:38   ` Antonino A. Daplas
2004-06-21  1:43 ` [patch] 2.6.7-mm1: R8169_NAPI help text Adrian Bunk
2004-06-21  1:55 ` [patch] 2.6.7-mm1: drivers/scsi/hosts.h -> scsi/scsi_host.h Adrian Bunk
2004-06-22  3:48   ` Jeff Garzik
2004-06-21  2:04 ` 2.6.7-mm1 Adrian Bunk
2004-06-22  5:33   ` 2.6.7-mm1 Sam Ravnborg
2004-07-17 20:46     ` [2.6 patch] move STANDALONE to drivers/base/Kconfig Adrian Bunk
2004-06-21  2:06 ` 2.6.7-mm1 linker trouble with CONFIG_FB_RIVA_I2C=y and modular I2C Matthias Andree
2004-06-21 15:29   ` Adrian Bunk [this message]
2004-06-22 15:11     ` [patch] " Matthias Andree
2004-06-21 10:48 ` 2.6.7-mm1 Dominik Karall
2004-06-21 11:00   ` 2.6.7-mm1 Andrew Morton
2004-06-21 11:43     ` 2.6.7-mm1 Dominik Karall
2004-06-23  7:28       ` 2.6.7-mm1 Daniele Venzano
2004-06-21 11:48 ` 2.6.7-mm1 Eric BEGOT
2004-06-21 14:25   ` 2.6.7-mm1 James Morris
2004-06-21 14:38     ` 2.6.7-mm1 Eric BEGOT
2004-06-22  0:15       ` 2.6.7-mm1 Adrian Bunk
2004-06-21 14:32 ` 2.6.7-mm1 (compile stats) John Cherry
2004-06-21 23:05 ` 2.6.7-mm1 I/O regression ? FabF
2004-06-21 23:18   ` FabF

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=20040621152905.GC28607@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=adaplas@hotpop.com \
    --cc=akpm@osdl.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