Yes, I'll cross out /arch/arm64/boot and arch/mm from my todo list. Do you mean the existing I-pipe code changes made to linux kernel module arch/arm/kernel do not apply to arch/arm64/kernel (for arm64)? I saw some I-pipe code in arch/arm/kernel dealing with interrupt, which made me wonder if similar code might have been needed in arch/arm64/kernel. I'll be glad to cross this one out too.
Thanks! Hongfei On Sat, Mar 21, 2015 at 6:11 AM, Gilles Chanteperdrix <[email protected]> wrote: > 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. _______________________________________________ Xenomai mailing list [email protected] http://www.xenomai.org/mailman/listinfo/xenomai
