| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 29 Apr 2011 13:26:25 +0200 From: Arnd Bergmann <arnd@...db.de> To: Benjamin Herrenschmidt <benh@...nel.crashing.org> Cc: "Russell King - ARM Linux" <linux@....linux.org.uk>, linaro-mm-sig@...ts.linaro.org, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [RFC] ARM DMA mapping TODO, v1 On Thursday 28 April 2011, Benjamin Herrenschmidt wrote: > > > > > > For PCI you can have the flag propagate from the PHB down, for busses > > > without a bus type (platform) then whoever instanciate them (the > > > platform code) can set that appropriately. > > > > How can you do that when it changes mid-bus heirarchy? I'm thinking > > of the situation where the DRM stuff is on a child bus below the > > root bus, and the root bus has DMA coherent devices on it but the DRM > > stuff doesn't. > > But that's not PCI right ? IE. with PCI, coherency is a property of the > PHB... That is my understanding at least, but I'd like to have a confirmation from the DRM folks. I believe that the PC graphics cards that have noncoherent DMA mappings are all of the unified memory (integrated into the northbridge) kind, so they are not on the same host bridge as all regular PCI devices, even if they appear as a PCI device. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists