All of lore.kernel.org
 help / color / mirror / Atom feed
From: vladimir.murzin@arm.com (Vladimir Murzin)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v3 PATCH 00/25] Allow NOMMU for MULTIPLATFORM
Date: Mon, 12 Dec 2016 09:28:03 +0000	[thread overview]
Message-ID: <584E6DA3.5070009@arm.com> (raw)
In-Reply-To: <238a0185-db3a-fa43-cd7d-91baebdb82d4@st.com>

Hi,

On 12/12/16 07:07, mickael guene wrote:
> Hi all,
> 
>  You can find an R toolchain here:
> https://github.com/mickael-guene/fdpic_manifest/releases/download/v7-r-1.0.1/toolset-v7-r-1.0.1-0-gbdcc6a7c-armv7-r.tgz
> 
>  It's an fdpic toolset for cortex-r cpu class. gcc version is
> quite old (4.7).
> 
>  Note also that generated code may crash on class A cpu due to
> generation of udiv/sdiv which is optional for class A.
> (cortex a15 is ok but not a9).
> 
> Hope it helps

Unfortunately, it doesn't help because it depends on FDPIC Linux patches
which are out of tree and no link has been given.

M-class toolchain should just work with A-class; you don't even need to
disable MMU to try it out after d782e42 ("ARM: 8594/1: enable binfmt_flat on
systems with an MMU").

Cheers
Vladimir

> 
> Regards
> Mickael
> 
> On 12/11/2016 09:01 PM, Peter Korsgaard wrote:
>>>>>>> "Afzal" == Afzal Mohammed <afzal.mohd.ma@gmail.com> writes:
>>
>> Hi,
>>
>>  >> You can build a toolchain and initramfs with Buildroot. Have a look at
>>  >> the stm32f429 nommu config:
>>  >>
>>  >> https://git.buildroot.net/buildroot/tree/configs/stm32f429_disco_defconfig
>>
>>  > iiuc, it builds one for Cortex-M. i already had a file system w/
>>  > busybox compiled using a Cortex-M toolchain (stolen from
>>  > Pengutronix's OSELAS.Toolchain), which works on Cortex M4 (Vybrid
>>  > VF610 M4 core). But it does not work here, i.e. on Cortex A, seems the
>>  > above mentioned also would have the same effect.
>>
>> Hmm, I'm not sure why a cortex-M toolchain wouldn't work on cortex-A, I
>> thought the 'M' instruction set was a pure subset of the 'A'.
>>
>>  > And in buildroot, couldn't see Cortex R option in menuconfig, and
>>  > selecting Cortex-A's excludes flat binary target & presents only with
>>  > ELF.
>>
>> We indeed don't have cortex-R support. I'm not aware of any cortex-R
>> Linux support.
>>
>> When you select a cortex-A variant, then we enable MMU support by
>> default, but you can disable it under toolchain options (Enable MMU) and
>> then the flat binary option is available.
>>
> 

  reply	other threads:[~2016-12-12  9:28 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 15:05 [RFC v3 PATCH 00/25] Allow NOMMU for MULTIPLATFORM Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 01/25] ARM: NOMMU: define stubs for fixup Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 02/25] ARM: NOMMU: define debug_ll_io_ini Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 03/25] ARM: debug: allow debug_ll_addr for NOMMU Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 04/25] ARM: NOMMU: define SECTION_xxx macros Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 05/25] ARM: NOMMU: define dummy user structure for feroceon Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 06/25] ARM: NOMMU: define __arm_ioremap_exec and pci_ioremap functions Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 07/25] ARM: NOMMU: relax restriction on MPU existence Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 08/25] ARM: NOMMU: fix head-nommu build for pre-ARMv7 CPUs Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 09/25] ARM: NOMMU: fix load of CONFIG_VECTORS_BASE Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 10/25] ARM: NOMMU: implement secondary_startup_arm Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 11/25] ARM: move arm_heavy_mb to MMU/noMMU neutral place Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 12/25] ARM: tlbflush: drop dependency on CONFIG_SMP Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 13/25] ARM: sleep: allow it to be build for R-class Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 14/25] ARM: setup: move call to erratum_a15_798181_init under CONFIG_MMU Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 15/25] ARM: kexec: disallow kexec for NOMMU builds Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 16/25] ARM: ep93xx: select ARM_PATCH_PHYS_VIRT for MMU builds only Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 17/25] ARM: omap: do not select HIGHMEM explicitly Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 18/25] ARM: sa1100: move CPU specific copy code under its own config Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 19/25] ARM: sa11x0: assabet: add dependency on MMU Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 20/25] ARM: i.MX: remove map_io callback Vladimir Murzin
2016-12-16  1:39   ` Shawn Guo
2016-12-02 15:05 ` [RFC v3 PATCH 21/25] PCI: tegra: limit to MMU build only Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 22/25] IB: add dependency on MMU Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 23/25] cnic: " Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 24/25] scsi: bnx2i: bnx2fc: " Vladimir Murzin
2016-12-02 15:05 ` [RFC v3 PATCH 25/25] ARM: Allow ARCH_MULTIPLATFORM to be selected for NOMMU Vladimir Murzin
2016-12-10 18:16 ` [RFC v3 PATCH 00/25] Allow NOMMU for MULTIPLATFORM Afzal Mohammed
2016-12-10 19:19   ` Arnd Bergmann
2016-12-11  6:33     ` Afzal Mohammed
2016-12-10 21:15   ` Peter Korsgaard
2016-12-11  7:01     ` Afzal Mohammed
2016-12-11 20:01       ` Peter Korsgaard
2016-12-12  7:07         ` mickael guene
2016-12-12  9:28           ` Vladimir Murzin [this message]
2016-12-12  9:44             ` mickael guene
2016-12-12 18:15         ` Afzal Mohammed
2016-12-13 17:10       ` Russell King - ARM Linux

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=584E6DA3.5070009@arm.com \
    --to=vladimir.murzin@arm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.