From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Hongfei Cheng <hongfei@mperpetuo.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] ARMv8 (ARM64) port of Xenomai
Date: Sat, 21 Mar 2015 14:11:11 +0100 [thread overview]
Message-ID: <20150321131111.GA20203@hermes.click-hack.org> (raw)
In-Reply-To: <CAKC9m6eFoRrFj_QteNeJmcbi+eir0SGzwoCTd2TVzPVuqDsiCQ@mail.gmail.com>
On Fri, Mar 20, 2015 at 05:06:36PM -0700, Hongfei Cheng wrote:
> Gilles - Thank you for sharing the link and updating us with your schedule.
>
> I just started to port the I-pipe and Xenomai-3 code for supporting
> the ARMv8 architecture. Based on my limited understanding of Xenomai,
> it appears that the following changes are required in order to get
> Xenomai-3 running on the ARMv8 SoC we plan to use (Qualcomm msm8994):
>
> 1). In vendor kernel tree, add I-pipe support to arm64 generic arch
> code: arch/arm64/boot, arch/arm64/kernel, etc.
> 2). In vendor kernel tree, add I-pipe support to arm64 MMU: arch/arm64/mm
> 3). In vendor kernel tree, add I-pipe support to platform-specific
> device tree: arm(64)/boot/dts/qcom
> 4). In vendor kernel tree, add I-pipe support to SoC and platform
> dependent drivers for arm64: drivers/gpio, drivers/irqchip(?),
> drivers/clocksource(?)
> 5). In xenomai-3 tree, support arm64 in Cobalt kernel: kernel/cobalt/arch/arm64
>
> Do you (and anyone else who's working on ARMv8) see any critical
> modules missing from my list?
No, but the contrary, there is no reason to touch boot, kernel, mm.
--
Gilles.
next prev parent reply other threads:[~2015-03-21 13:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 16:45 [Xenomai] ARMv8 (ARM64) port of Xenomai Hongfei Cheng
2015-03-20 18:13 ` Gilles Chanteperdrix
2015-03-21 0:06 ` Hongfei Cheng
2015-03-21 13:11 ` Gilles Chanteperdrix [this message]
2015-03-21 13:21 ` Gilles Chanteperdrix
2015-03-23 6:01 ` Hongfei Cheng
2015-03-23 9:03 ` Jan Kiszka
2015-03-23 9:53 ` Gilles Chanteperdrix
2015-03-23 14:00 ` Jan Kiszka
2015-03-23 15:25 ` Gilles Chanteperdrix
2015-03-24 14:40 ` Jan Kiszka
2015-03-24 15:27 ` Gilles Chanteperdrix
2015-04-02 8:12 ` Hongfei Cheng
2015-04-02 9:04 ` Gilles Chanteperdrix
2015-04-02 17:56 ` Hongfei Cheng
2015-03-23 11:50 ` Jorge Ramirez Ortiz
2015-03-23 5:56 ` Hongfei Cheng
-- strict thread matches above, loose matches on Subject: below --
2015-03-26 22:58 Don Mahurin
2015-03-26 23:05 ` Gilles Chanteperdrix
2015-03-26 23:29 ` Don Mahurin
2015-03-27 0:13 ` Lennart Sorensen
2015-03-27 7:55 ` Gilles Chanteperdrix
2015-02-16 20:15 Gary Gitelson
2015-02-16 20:44 ` Gilles Chanteperdrix
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=20150321131111.GA20203@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=hongfei@mperpetuo.com \
--cc=xenomai@xenomai.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.