From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: John Linville <linville@tuxdriver.com>
Cc: wireless <linux-wireless@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
Pavel Roskin <proski@gnu.org>
Subject: [PATCH] Don't build SSB modules when SSB isn't present
Date: Fri, 06 Nov 2009 13:53:45 -0800 [thread overview]
Message-ID: <4AF49AE9.1040603@redfish-solutions.com> (raw)
From: Philip A Prindeville <philipp@redfish-solutions.com>
If you're building for a platform that has (for example) no SSB,
then having a single knob to turn to disable this is a major
win. Especially if more devices get add later that are SSB-based.
Tested.
Signed-off-by: Philip A Prindeville <philipp@redfish-solutions.com>
---
config.mk | 14 ++++++++------
1 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/config.mk b/config.mk
index ce70832..49be2d0 100644
--- a/config.mk
+++ b/config.mk
@@ -9,6 +9,8 @@ ifeq ($(wildcard $(KLIB_BUILD)/.config),)
CONFIG_PCI=y
CONFIG_USB=y
CONFIG_PCMCIA=y
+ CONFIG_SSB_POSSIBLE=y
+ CONFIG_SSB=m
else
include $(KLIB_BUILD)/.config
endif
@@ -218,6 +220,11 @@ CONFIG_IPW2200_QOS=y
#
# % echo 1 > /sys/bus/pci/drivers/ipw2200/*/rtap_iface
+ifneq ($(CONFIG_SSB),)
+# Sonics Silicon Backplane
+CONFIG_SSB_SPROM=y
+# CONFIG_SSB_DEBUG=y
+
CONFIG_SSB_BLOCKIO=y
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
@@ -229,6 +236,7 @@ endif
# CONFIG_SSB_DEBUG=y
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y
+endif
CONFIG_P54_PCI=m
@@ -397,12 +405,6 @@ CONFIG_WL1251_SPI=m
CONFIG_WL1251_SDIO=m
CONFIG_WL1271=m
-# Sonics Silicon Backplane
-CONFIG_SSB_POSSIBLE=y
-CONFIG_SSB=m
-CONFIG_SSB_SPROM=y
-# CONFIG_SSB_DEBUG=y
-
ifdef CONFIG_COMPAT_WIRELESS_27
CONFIG_LIBERTAS=n
else
next reply other threads:[~2009-11-06 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 21:53 Philip A. Prindeville [this message]
2009-11-13 19:28 ` [PATCH] Don't build SSB modules when SSB isn't present Luis R. Rodriguez
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=4AF49AE9.1040603@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=proski@gnu.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;
as well as URLs for NNTP newsgroup(s).