From: catalin.marinas@arm•com (Catalin Marinas)
To: linux-arm-kernel@lists•infradead.org
Subject: Question on ARM Cortex R4 support in Linux
Date: Mon, 20 Feb 2012 10:01:22 +0000 [thread overview]
Message-ID: <20120220100122.GB14018@arm.com> (raw)
In-Reply-To: <4F4217F7.6050908@st.com>
On Mon, Feb 20, 2012 at 09:52:55AM +0000, Armando Visconti wrote:
> >>>> Has anybody used it on Cortex R4 based platform ?
> >>>
> >>> In theory Linux support for R4 should just work (once CONFIG_MMU is
> >>> disabled). I used to test it in the past regularly but not recently.
> >>
> >> Great. I was planning to use linux-3.2, I hope the support is there ?
> >
> > It's been there for years, but some bit-rotting may have occurred.
>
> I'm assuming you have tried it on a FPGA solution, is that correct?
It may have been a real silicon (core tile for a RealView EB board), I
don't remember the details.
> We are planning to buy a Cortex-R4 board from ARM.
> Lionel Belnet suggested to buy Versatile + a CoreTile with Cortex-R4F
> r1p2 Test Chip on it.
>
> Is there any Linux/ucLinux support already offered for this solution?
On www.arm.com/linux there is a uClinux tab with images for download,
though the kernel is 2.6.35. Anyway, you can always get a newer kernel
and just disable CONFIG_MMU for a RealView/EB board with ARMv6
processor.
> Any other idea?
I can't really tell what other R4 platforms are around.
--
Catalin
next prev parent reply other threads:[~2012-02-20 10:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 10:49 Question on ARM Cortex R4 support in Linux shiraz hashim
2012-02-13 10:53 ` Catalin Marinas
2012-02-13 10:59 ` shiraz hashim
2012-02-13 11:07 ` Catalin Marinas
2012-02-20 9:52 ` Armando Visconti
2012-02-20 10:01 ` Catalin Marinas [this message]
2012-02-20 10:26 ` Armando Visconti
2012-02-20 10:41 ` Catalin Marinas
2012-02-20 17:02 ` Catalin Marinas
2012-02-20 18:21 ` Armando Visconti
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=20120220100122.GB14018@arm.com \
--to=catalin.marinas@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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