linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gerg@uclinux.org (Greg Ungerer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: versatile: support configuring versatile machine for no-MMU
Date: Thu, 8 Dec 2016 00:34:44 +1000	[thread overview]
Message-ID: <d64c0ccc-8db9-a565-7415-7108965a0e0e@uclinux.org> (raw)
In-Reply-To: <CACRpkdZywn46QbnvKcN-jkt43Vf+GBSNQkLgnnNg-DC-8aSO5w@mail.gmail.com>

Hi Linus,

On 08/12/16 00:11, Linus Walleij wrote:
> On Wed, Dec 7, 2016 at 7:59 AM, Greg Ungerer <gerg@uclinux.org> wrote:
>
>> The motivation for this is that the versatile machine is well supported
>> in qemu. And this provides an excellent platform for development and
>> testing no-MMU support on ARM in general.
>>
>> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
>
> Pretty cool eh?

Yep :-)


> Have you tested it on real hardware?

No, I don't have a Versatile board, or access to one...


> Otherwise I can test it if I have a git branch
> I can pull in and compile.

I have been stashing the changes here for now:

git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git

in the armnommu branch.


> Another target I had in mind was the Integrator which
> incidentally supports a bunch of the old noMMU core
> tiles where we can swap in an ARM946, which I guess
> could work with this?

It should do, or at least should be able to be made to work with it.


>> --- a/arch/arm/mach-versatile/Kconfig
>> +++ b/arch/arm/mach-versatile/Kconfig
>> @@ -1,12 +1,13 @@
>>  config ARCH_VERSATILE
>>         bool "ARM Ltd. Versatile family"
>> -       depends on ARCH_MULTI_V5
>> +       depends on ARCH_MULTI_V5 || ARM_SINGLE_ARMV5
>>         select ARM_AMBA
>>         select ARM_TIMER_SP804
>>         select ARM_VIC
>>         select CLKSRC_VERSATILE
>>         select COMMON_CLK_VERSATILE
>>         select CPU_ARM926T
>> +       select GPIOLIB
>
> Not really related but I don't mind.

No, probably strictly not. But without this here we lose CONFIG_GPIO
for the no-MMU case. When CONFIG_MMU was enabled it was being selected
via some other path through arch/arm/Kconfig - I don't recall at the
moment where exactly.


> Acked-by: Linus Walleij <linus.walleij@linaro.org>

Thanks
Greg

      parent reply	other threads:[~2016-12-07 14:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07  6:59 [PATCH 3/4] ARM: versatile: empty Makefile.boot needed for no-MMU compile Greg Ungerer
2016-12-07  6:59 ` [PATCH 4/4] ARM: versatile: support configuring versatile machine for no-MMU Greg Ungerer
2016-12-07 14:11   ` Linus Walleij
2016-12-07 14:33     ` Vladimir Murzin
2016-12-09  3:02       ` Greg Ungerer
2016-12-09 20:29       ` Russell King - ARM Linux
2016-12-12  5:48         ` Greg Ungerer
2016-12-12  5:50         ` [PATCHv2 4/4] ARM: versatile: support configuring versatile machine for, no-MMU Greg Ungerer
2016-12-12 13:06         ` [PATCH 4/4] ARM: versatile: support configuring versatile machine for no-MMU Vladimir Murzin
2016-12-07 14:34     ` Greg Ungerer [this message]

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=d64c0ccc-8db9-a565-7415-7108965a0e0e@uclinux.org \
    --to=gerg@uclinux.org \
    --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).