All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: "prem.de.ms" <prem.de.ms@gmx.de>,
	linux-kernel@vger.kernel.org, kraxel@bytesex.org,
	Radoslaw Szkodzinski <astralstorm@gmail.com>
Subject: Re: 2.6.10 compile error - blackbird_load_firmware (fwd)
Date: Sun, 16 Jan 2005 08:23:46 +0100	[thread overview]
Message-ID: <20050116072345.GQ4274@stusta.de> (raw)

The patch below by Radoslaw Szkodzinski <astralstorm@gmail.com> still 
applies and seems to be still required in 2.6.11-rc1-mm1.


Signed-off-by: Adrian Bunk <bunk@stusta.de>



----- Forwarded message from Radoslaw Szkodzinski <astralstorm@gmail.com> -----

Date:	Mon, 3 Jan 2005 15:27:30 +0100
From: Radoslaw Szkodzinski <astralstorm@gmail.com>
To: "prem.de.ms" <prem.de.ms@gmx.de>
Cc: linux-kernel@vger.kernel.org, kraxel@bytesex.org
Subject: Re: 2.6.10 compile error - blackbird_load_firmware

On Monday 27 of December 2004 23:00, prem.de.ms wrote:
> Hello,
>
> I get the following error message when I try to compile the new
> 2.6.10-kernel:
>
> <snip>
> Seems like the Conexant drivers are broken because the kernel compiles
> when I uncheck them.
>
It seems Conexant uses the firmware loader as well as I2C w/o requiring them.
Patch attached.

--- linux/drivers/media/video/Kconfig~	2005-01-03 15:24:46.669675320 +0100
+++ linux/drivers/media/video/Kconfig	2005-01-03 15:24:46.680673445 +0100
@@ -303,8 +303,9 @@
 
 config VIDEO_CX88
 	tristate "Conexant 2388x (bt878 successor) support"
-	depends on VIDEO_DEV && PCI && EXPERIMENTAL
+	depends on VIDEO_DEV && PCI && I2C && EXPERIMENTAL
 	select I2C_ALGOBIT
+	select FW_LOADER
 	select VIDEO_BTCX
 	select VIDEO_BUF
 	select VIDEO_TUNER



----- End forwarded message -----



                 reply	other threads:[~2005-01-16  7:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050116072345.GQ4274@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=astralstorm@gmail.com \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prem.de.ms@gmx.de \
    /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.