From: Greg Ungerer <gerg@snapgear.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: gerg@uclinux.org, jbarnes@virtuousgeek.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [2.6 patch] m68knommu: let PCI depend on BROKEN
Date: Mon, 25 Aug 2008 16:16:12 +1000 [thread overview]
Message-ID: <48B24E2C.9060703@snapgear.com> (raw)
In-Reply-To: <20080819134718.GH8852@cs181140183.pp.htv.fi>
Hi Adrian,
Adrian Bunk wrote:
> There exists blackfin hardware with PCI support, but the support
> currently in the kernel fails to build starting with:
>
> <-- snip -->
>
> ...
> CC init/main.o
> In file included from dma-mapping.h:5,
> from dma-mapping.h:52,
> from dmaengine.h:29,
> from skbuff.h:29,
> from netlink.h:155,
> from genetlink.h:4,
> from genetlink.h:4,
> from taskstats_kern.h:12,
> from main.c:46:
> dma-mapping.h: In function 'dma_supported': ma-mapping.h:24:
> error: implicit declaration of function 'pci_dma_supported'
> ...
> make[2]: *** [init/main.o] Error 1
I think we should just remove the underlying comempci access
code which is the only user of this (arch/m68knommu/kernel/comempci.c).
Nobody has used it in a very long time. And the hardware itself is
old, and completely brain-damaged by design.
Regards
Greg
> <-- snip -->
>
> Signed-off-by: Adrian Bunk <bunk@kernel.org>
>
> ---
> 3bdc07c86b6fd5fc18b7676a75c3ff907e00e807
> diff --git a/arch/m68knommu/Kconfig b/arch/m68knommu/Kconfig
> index 2e7515e..77a5bdf 100644
> --- a/arch/m68knommu/Kconfig
> +++ b/arch/m68knommu/Kconfig
> @@ -702,6 +702,7 @@ menu "Bus options (PCI, PCMCIA, EISA, MCA, ISA)"
>
> config PCI
> bool "PCI support"
> + depends on BROKEN
> help
> Support for PCI bus.
>
>
>
--
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Dude EMAIL: gerg@snapgear.com
SnapGear -- a Secure Computing Company PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2008-08-25 6:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 13:47 [2.6 patch] m68knommu: let PCI depend on BROKEN Adrian Bunk
2008-08-19 14:13 ` Geert Uytterhoeven
2008-08-19 14:32 ` Adrian Bunk
2008-08-19 15:05 ` Matthew Wilcox
2008-08-22 3:44 ` Bryan Wu
2008-08-25 6:16 ` Greg Ungerer [this message]
2008-08-25 20:43 ` [RFC: 2.6 patch] m68knommu: remove the broken COMEMPCI code Adrian Bunk
2008-08-29 4:13 ` Greg Ungerer
2008-08-29 7:01 ` Adrian Bunk
2008-08-29 7:31 ` Geert Uytterhoeven
2008-08-31 16:10 ` [2.6 patch] m68k: remove the dead PCI code Adrian Bunk
2008-09-03 7:22 ` Geert Uytterhoeven
2008-09-06 12:23 ` Geert Uytterhoeven
2008-09-09 5:06 ` Jesse Barnes
2008-09-09 7:11 ` Geert Uytterhoeven
2008-09-25 13:31 ` Adrian Bunk
2008-08-29 11:07 ` [RFC: 2.6 patch] m68knommu: remove the broken COMEMPCI code Greg Ungerer
2008-08-31 16:10 ` [2.6 patch] m68knommu: remove the eLIA support Adrian Bunk
2008-08-31 16:10 ` [2.6 patch] m68knommu: remove the unused PCI option Adrian Bunk
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=48B24E2C.9060703@snapgear.com \
--to=gerg@snapgear.com \
--cc=bunk@kernel.org \
--cc=gerg@uclinux.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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