From: <gerg@snapgear.com>
To: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org
Cc: Greg Ungerer <gerg@uclinux.org>
Subject: [PATCH 4/4] m68k: allow PCI bus to be enabled for ColdFire m54xx CPUs
Date: Fri, 29 Jun 2012 15:17:50 +1000 [thread overview]
Message-ID: <1340947070-10672-5-git-send-email-gerg@snapgear.com> (raw)
In-Reply-To: <1340947070-10672-1-git-send-email-gerg@snapgear.com>
From: Greg Ungerer <gerg@uclinux.org>
All support code for the PCI bus hardware on the ColdFire 547x and 548x
CPUs is now in. Allow enabling of CONFIG_PCI for them.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
---
arch/m68k/Kconfig.bus | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/arch/m68k/Kconfig.bus b/arch/m68k/Kconfig.bus
index 3adb499..ffc0601 100644
--- a/arch/m68k/Kconfig.bus
+++ b/arch/m68k/Kconfig.bus
@@ -48,6 +48,13 @@ config ISA
config GENERIC_ISA_DMA
def_bool ISA
+config PCI
+ bool "PCI support"
+ depends on M54xx
+ help
+ Enable the PCI bus. Support for the PCI bus hardware built into the
+ ColdFire 547x and 548x processors.
+
source "drivers/pci/Kconfig"
source "drivers/zorro/Kconfig"
--
1.7.0.4
prev parent reply other threads:[~2012-06-29 5:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 5:17 [PATCH 0/4] m68k: ColdFire PCI bus support gerg
2012-06-29 5:17 ` [PATCH 1/4] m68k: common PCI support definitions and code gerg
2012-06-29 5:42 ` Geert Uytterhoeven
2012-06-29 6:03 ` Greg Ungerer
2012-06-29 5:45 ` Geert Uytterhoeven
2012-06-29 5:17 ` [PATCH 2/4] m68k: add PCI bus support for the ColdFire M54xx SoC family gerg
2012-06-29 5:17 ` [PATCH 3/4] m68k: add IO access definitions to support PCI on ColdFire platforms gerg
2012-06-29 5:46 ` Geert Uytterhoeven
2012-06-29 5:17 ` gerg [this message]
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=1340947070-10672-5-git-send-email-gerg@snapgear.com \
--to=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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