On Mon, Sep 07, 2015 at 03:40:36PM -0400, Nicolas Pitre wrote: > On Mon, 7 Sep 2015, Arnd Bergmann wrote: > > > On Thursday 03 September 2015 21:24:00 Nicolas Pitre wrote: > > > If 768MB targets were common place then it could be worth changing the > > > default vmalloc size to accommodate this memory size and testing all the > > > other targets to make sure no regressions are introduced. But given it > > > is easy to change the default via the kernel cmdline, and that you lose > > > only 8 MB otherwise, I don't think it is worth the trouble and/or the > > > risk. > > > > Agreed. > > Well... I think there is a better solution.
Doesn't this clash with things like: #define UNCACHEABLE_ADDR 0xff000000 /* IRQ_STAT */ ? -- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
