From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 03/11] ARM: omap: do not select HIGHMEM explicitly
Date: Tue, 22 Nov 2016 09:51:36 +0000 [thread overview]
Message-ID: <20161122095136.GU1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <1479806768-39911-4-git-send-email-vladimir.murzin@arm.com>
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.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-11-22 9:51 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 9:25 [RFC PATCH 00/11] Allow NOMMU for MULTIPLATFORM Vladimir Murzin
2016-11-22 9:25 ` [RFC PATCH 01/11] ARM: NOMMU: define stubs for fixup Vladimir Murzin
2016-11-22 9:48 ` Russell King - ARM Linux
2016-11-22 9:54 ` Vladimir Murzin
2016-11-22 9:25 ` [RFC PATCH 02/11] ARM: ep93xx: select ARM_PATCH_PHYS_VIRT for MMU builds only Vladimir Murzin
2016-11-22 9:26 ` [RFC PATCH 03/11] ARM: omap: do not select HIGHMEM explicitly Vladimir Murzin
2016-11-22 9:51 ` Russell King - ARM Linux [this message]
2016-11-23 15:49 ` Tony Lindgren
2016-11-23 16:08 ` Vladimir Murzin
2016-11-22 9:26 ` [RFC PATCH 04/11] PCI: tegra: limit to MMU build only Vladimir Murzin
2016-11-22 9:31 ` Arnd Bergmann
2016-11-22 9:40 ` Vladimir Murzin
2016-11-22 9:54 ` Arnd Bergmann
2016-11-22 9:58 ` Vladimir Murzin
2016-11-22 11:26 ` Thierry Reding
2016-11-25 10:49 ` Vladimir Murzin
2016-11-22 16:15 ` Stephen Warren
2016-11-22 21:16 ` Arnd Bergmann
2016-11-22 22:27 ` Stephen Warren
2016-11-22 22:52 ` Arnd Bergmann
2016-11-22 9:26 ` [RFC PATCH 05/11] ARM: move arm_heavy_mb to MMU/noMMU neutral place Vladimir Murzin
2016-11-22 9:26 ` [RFC PATCH 06/11] ARM: tlbflush: drop dependency on CONFIG_SMP Vladimir Murzin
2016-11-22 10:03 ` Russell King - ARM Linux
2016-11-22 13:36 ` Vladimir Murzin
2016-11-24 17:41 ` Vladimir Murzin
2016-11-22 9:26 ` [RFC PATCH 07/11] ARM: sleep: allow it to be build for R-class Vladimir Murzin
2016-11-22 9:26 ` [RFC PATCH 08/11] ARM: NOMMU: define debug_ll_io_ini Vladimir Murzin
2016-11-22 9:26 ` [RFC PATCH 09/11] ARM: NOMMU: define SECTION_xxx macros Vladimir Murzin
2016-11-22 10:07 ` Russell King - ARM Linux
2016-11-22 11:50 ` Vladimir Murzin
2016-11-22 11:54 ` Russell King - ARM Linux
2016-11-22 17:03 ` Vladimir Murzin
2016-11-24 17:38 ` Vladimir Murzin
2016-11-22 9:26 ` [RFC PATCH 10/11] ARM: NOMMU: define __arm_ioremap_exec and pci_ioremap functions Vladimir Murzin
2016-11-22 9:26 ` [RFC PATCH 11/11] ARM: Allow ARCH_MULTIPLATFORM to be selected for NOMMU Vladimir Murzin
2016-11-22 10:17 ` Arnd Bergmann
2016-11-22 16:57 ` Vladimir Murzin
2016-11-23 15:48 ` Afzal Mohammed
2016-11-23 16:07 ` Vladimir Murzin
2016-11-24 17:28 ` Afzal Mohammed
2016-11-24 17:33 ` Vladimir Murzin
2016-11-24 18:09 ` Afzal Mohammed
2016-11-23 19:16 ` Russell King - ARM Linux
2016-11-24 17:25 ` Afzal Mohammed
2016-11-24 17:35 ` Russell King - ARM Linux
2016-11-24 18:07 ` Afzal Mohammed
2016-11-24 18:45 ` Russell King - ARM Linux
2016-11-25 11:20 ` Vladimir Murzin
2016-11-23 15:55 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161122095136.GU1041@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).