From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 21 Mar 2015 14:11:11 +0100 From: Gilles Chanteperdrix Message-ID: <20150321131111.GA20203@hermes.click-hack.org> References: <20150320181308.GA27775@hermes.click-hack.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Xenomai] ARMv8 (ARM64) port of Xenomai List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Hongfei Cheng Cc: xenomai@xenomai.org 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.