Messages in this thread | | | Date | Mon, 30 May 2011 01:33:26 +0400 | Subject | Re: IrDA driver fails on PXA255 | From | Dmitry Eremin-Solenikov <> |
| |
On Mon, May 30, 2011 at 1:17 AM, David Rientjes <rientjes@google.com> wrote: > On Sun, 29 May 2011, Dmitry Eremin-Solenikov wrote: > >> What about changing your patch for less intrusive one (to emit a >> WARN_ON) for at least one >> or two major releases and only then changing it back to the current state? >> > > That would return memory that is not guaranteed to be within the first > 16MB of address space, so a GFP_DMA allocation would succeed with memory > not from ZONE_DMA. That's an invalid configuration, so users, including > you, should at least edit their .config by hand to enable CONFIG_ZONE_DMA > as a workaround. Then, we should try to fix up the Kconfig entries for > drivers requiring DMA allocations to select CONFIG_ZONE_DMA or fix > defconfigs when DMA is known to be needed for a device.
Am I right that this was the previous behaviour for GFP_DMA allocations w/o CONFIG_ZONE_DMA? If so, we can have it (probably) for one more major release to get all warnings.
-- With best wishes Dmitry -- 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/
| |