linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: add ARM_SINGLE_ARMV7 as config option
Date: Fri, 10 Feb 2017 16:39:08 +0000	[thread overview]
Message-ID: <20170210163908.GL27312@n2100.armlinux.org.uk> (raw)
In-Reply-To: <25202835.AdbHsoUg0y@wuerfel>

On Fri, Feb 10, 2017 at 02:05:43PM +0100, Arnd Bergmann wrote:
> And I really don't like adding new top-level for a platform here, it
> brings us back to the same problems we had before we moved most platforms
> to ARCH_MULTIPLATFORM, and it doesn't solve the remaining problems we still
> have:

It's the least evil solution.

> - In some platforms, the decision would have to be done on a per-board
>   level, as each board can have its memory at a different location
>   base on which chipselect line got connected to the RAM and NOR flash
>   respectively

Right, but that's something we _had_ solved before multiplatform came
along.

> - Some (few) platforms actually have separate top-level Kconfig options
>   but are actually very closely related and you could have a kernel
>   for all of them even with !MMU and XIP_KERNEL. The most important
>   one here is ARM Versatile/Realview/Integrator/Vexpress that have
>   more in common than things we put behind a common Kconfig option in
>   other platforms.

If you think that Versatile + Realview + Integrator + Vexpress should
be lumped into one kernel image for !MMU and XIP_KERNEL then you're
wrong - from what I remember, their RAM and flash locations are quite
different which rules it out.

The biggest thing that matters for !MMU and XIP_KERNEL is the location
of flash and RAM.  If those are not compatible, !MMU and XIP_KERNEL
has no chance of working.

> - CONFIG_DEBUG_UNCOMPRESS has a very similar requirements to
>   XIP_KERNEL and !MMU, and we currently allow it for any machine,
>   with a lot of flexibility in configuring that always breaks
>   running on any machine other than the one you are targetting.

Right, but that's debug, not core kernel configuration.

-- 
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.

  parent reply	other threads:[~2017-02-10 16:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09  3:30 [PATCH 0/2] ARM: ARMv7 (with MMU) XIP without ARCH_MULTIPLATFORM Chris Brandt
2017-02-09  3:30 ` [PATCH 1/2] ARM: add ARM_SINGLE_ARMV7 as config option Chris Brandt
2017-02-09  3:37   ` Florian Fainelli
2017-02-09  3:50     ` Chris Brandt
2017-02-09 19:53       ` Florian Fainelli
2017-02-09 20:21         ` Chris Brandt
2017-02-10 13:05           ` Arnd Bergmann
2017-02-10 14:17             ` Chris Brandt
2017-02-10 15:53               ` Arnd Bergmann
2017-02-10 16:39             ` Russell King - ARM Linux [this message]
2017-02-13 20:45               ` Arnd Bergmann
2017-02-09  3:30 ` [PATCH 2/2] ARM: shmobile: add renesas soc as a top level selection Chris Brandt

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=20170210163908.GL27312@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).