[RFC PATCH 03/11] ARM: omap: do not select HIGHMEM explicitly
Tony Lindgren
tony at atomide.com
Wed Nov 23 07:49:57 PST 2016
* Russell King - ARM Linux <linux at armlinux.org.uk> [161122 01:51]:
> On Tue, Nov 22, 2016 at 09:26:00AM +0000, Vladimir Murzin wrote:
> > Explicit selection of HIGHMEM breaks NOMMU builds. It seems that
> > HIGHMEM is user selectable option, so probably it would be better to
> > let user to make a decision on this options or, at least, move it to
> > defconfig.
>
> That's kind of the point of ARCH_OMAP2PLUS_TYPICAL - it's a user
> option to let the user select a range of options for typical OMAP2+
> configurations, so that the user doesn't have to dig around looking
> for multiple options, some of which are hard requirements for OMAP
> to be functional. OMAP is a particularly difficult case because the
> hardware tends to be very complex.
>
> However, HIGHMEM should never be a requirement to boot, so this looks
> sane.
Yeah we can add that to the defconfig:
Acked-by: Tony Lindgren <tony at atomide.com>
More information about the linux-arm-kernel
mailing list