From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 2 Apr 2015 11:04:00 +0200 From: Gilles Chanteperdrix Message-ID: <20150402090400.GC31175@hermes.click-hack.org> References: <20150321131111.GA20203@hermes.click-hack.org> <20150321132130.GC20203@hermes.click-hack.org> <550FD6CA.7080407@web.de> <20150323095340.GA5299@hermes.click-hack.org> <55101C6F.2030207@web.de> <20150323152540.GC5299@hermes.click-hack.org> <55117747.6040807@web.de> <20150324152749.GA15125@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: Jan Kiszka , xenomai@xenomai.org On Thu, Apr 02, 2015 at 01:12:11AM -0700, Hongfei Cheng wrote: > Thank you all again for the clear and prompt responses, along with > the informative discussions. > > A follow-up question to the kernel module(s) requiring changes for > supporting I-pipe for Aarch64/arm64: After enabling I-pipe (but with > xenomai-3 disabled) in the kernel with the ipipe-core patch for > Aarch32/arm, building the Aarch64 kernel image shows clear dependency on > I-pipe specific code in arch/arm64/kernel. This observation appears > to deviate from Gilles' earlier advice -- "there is no reason to touch > boot, kernel, mm". > > Since the Aarch64 code in arch/arm64/kernel differs quite a bit from the > Aarch32 code in arch/arm/kernel, porting the ipipe-core code from > arch/arm/kernel to arch/arm64/kernel will require significant amount of > work. I'd appreciate if anyone can affirm or refute the need to touch > arch/arm64/kernel for Aarch64/arm64, before I go too far and veer off the > road. Speaking in directory/files is meaningless, what matters is what you change. I think I have given you a list of what to change already. If some files to change are in the kernel directory, then OK, I was wrong. -- Gilles.