From: Adrian Bunk <bunk@stusta.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
mb@bu3sch.de, netdev@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: SSB/b44 build failure
Date: Sat, 10 Mar 2007 16:38:16 +0100 [thread overview]
Message-ID: <20070310153816.GP3441@stusta.de> (raw)
In-Reply-To: <20070310150346.GB5062@tuxdriver.com>
On Sat, Mar 10, 2007 at 10:03:46AM -0500, John W. Linville wrote:
> On Fri, Mar 09, 2007 at 07:14:09PM -0800, Randy Dunlap wrote:
> > Hi,
> >
> > In 2.6.21-rc3-mm2, with CONFIG_SSB=y but all other SSB kconfig
> > symbols disabled, I get this (on x86_64):
> >
> > drivers/built-in.o: In function `b44_init':
> > b44.c:(.init.text+0x6e04): undefined reference to `ssb_pcihost_register'
> > b44.c:(.init.text+0x6e2c): undefined reference to `ssb_pcihost_unregister'
> > drivers/built-in.o: In function `b44_cleanup':
> > b44.c:(.exit.text+0x63b): undefined reference to `ssb_pcihost_unregister'
> > make: *** [.tmp_vmlinux1] Error 1
>
> FWIW, this is coming from the port of b44 to use the SSB bus which
> I'm carrying in the wireless-dev tree.
>
> SSB (i.e. "Sonics Silicon Backplane") is a bus used in Broadcom SoCs
> including the b44 and bcm43xx hardware. The SSB bus driver and the
> b44 port to SSB is being developed by Michael Buesch, the maintainer of
> the bcm43xx driver. I've been carrying the b44 SSB port in my tree for
> Michael's convenience. Just an FYI for those wondering what SSB is...
>
> John
>
> P.S. How about this patch?
>
> From: John W. Linville <linville@tuxdriver.com>
>
> [PATCH] b44: make B44_PCI select SSB_PCIHOST in drivers/net/Kconfig
>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> ---
> drivers/net/Kconfig | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
> index 6a4325b..b2e1deb 100644
> --- a/drivers/net/Kconfig
> +++ b/drivers/net/Kconfig
> @@ -1402,6 +1402,7 @@ config B44
> config B44_PCI
> bool "Broadcom 4400 PCI device support"
> depends on B44 && NET_PCI
> + select SSB_PCIHOST
> default y
> help
> Support for b44 PCI devices.
This also requires a depends or select on SSB.
> John W. Linville
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:[~2007-03-10 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 3:14 SSB/b44 build failure Randy Dunlap
2007-03-10 15:03 ` John W. Linville
2007-03-10 15:38 ` Adrian Bunk [this message]
2007-03-10 16:22 ` John W. Linville
2007-03-11 17:22 ` Adrian Bunk
2007-03-10 17:33 ` Michael Buesch
2007-03-10 18:05 ` Christoph Hellwig
2007-03-10 19:27 ` Michael Buesch
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=20070310153816.GP3441@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@linux-foundation.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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).