All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Hongfei Cheng <hongfei@mperpetuo.com>
Cc: Jan Kiszka <jan.kiszka@web.de>, xenomai@xenomai.org
Subject: Re: [Xenomai] ARMv8 (ARM64) port of Xenomai
Date: Thu, 2 Apr 2015 11:04:00 +0200	[thread overview]
Message-ID: <20150402090400.GC31175@hermes.click-hack.org> (raw)
In-Reply-To: <CAKC9m6e24UQg6NiYc+tJbQH-txLF6fvYKH-jca0oEnVMavmjpQ@mail.gmail.com>

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.


  reply	other threads:[~2015-04-02  9:04 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
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 [this message]
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=20150402090400.GC31175@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=hongfei@mperpetuo.com \
    --cc=jan.kiszka@web.de \
    --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.