All of lore.kernel.org
 help / color / mirror / Atom feed
From: armando.visconti@st.com (Armando Visconti)
To: linux-arm-kernel@lists.infradead.org
Subject: Question on ARM Cortex R4 support in Linux
Date: Mon, 20 Feb 2012 19:21:17 +0100	[thread overview]
Message-ID: <4F428F1D.3080806@st.com> (raw)
In-Reply-To: <CAHkRjk5Be=5A1tHiRXGuQAgdLyxQDpiZwJD1ryx3T6syKaLwxg@mail.gmail.com>

>>>> 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.
>>
>> So, you are suggesting that we can got for a RealView + CoreTile with
>> Cortex-R4F testchip instead of versatile?
>
> I looked at the www.arm.com boards page and marketing now calls the
> RealView EB (Emulation Baseboard) a Versatile board. I lost track of
> the naming :). But yes, Versatile + R4 tile is the same as the one I
> tested. In Linux just make sure that you configure it as RealView EB.
>

Thx very much Catalin.

It is very clear and helpful from you!

Rgds,
Arm

      reply	other threads:[~2012-02-20 18:21 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
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 [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=4F428F1D.3080806@st.com \
    --to=armando.visconti@st.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.