[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120922.160027.1528491047223302539.davem@davemloft.net>
Date: Sat, 22 Sep 2012 16:00:27 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: benh@...nel.crashing.org
Cc: sfr@...b.auug.org.au, paulus@...ba.org,
linuxppc-dev@...ts.ozlabs.org, mika.westerberg@...ux.intel.com,
netdev@...r.kernel.org, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree
(net-next tree related)
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Date: Sat, 22 Sep 2012 07:46:40 +1000
> Right, but on ppc, GFP_DMA is a nop (no separate ZONE_DMA, or rather all
> of memory is ZONE_DMA). It's always been like that afaik.
>
> We could support ISA device limited addressability using the iommu but
> that would involve a map/unmap type API (which I remember we did support
> in the old days by passing NULL to pci_map_*, but we dropped that along
> the way).
I think I'm going to just end up restricting this driver to X86
as was originally suggested.
There seems to be no real consistent Kconfig protection for users
of isa_virt_to_bus() and friends.
We know that ISA_DMA_API doesn't do it, and ISA doesn't do it either
as powerpc also allows that to bet set for CHRP and friends.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists