![]() | |||||||||||
Messages in this thread |
> introduce-config_zone_dma.patch > optional-zone_dma-in-the-vm.patch > optional-zone_dma-in-the-vm-tidy.patch > optional-zone_dma-for-i386.patch > optional-zone_dma-for-x86_64.patch > optional-zone_dma-for-ia64.patch > remove-zone_dma-remains-from-parisc.patch > remove-zone_dma-remains-from-sh-sh64.patch Would it not make sense to define what ZONE_DMA actually means consistently before trying to change it? The current mess across different architectures seems like a disaster area to me. What DOES requesting ZONE_DMA from a driver actually mean? M. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2006-09-21 02:13 [from the cache] ©2003-2008 | |||||||||||