All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: "Deniz Uğur" <deniz343@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [I-PIPE][ARM64] Experimenting on Jetson Xavier
Date: Sun, 21 Feb 2021 17:29:07 +0100	[thread overview]
Message-ID: <87a6rx4c6k.fsf@xenomai.org> (raw)
In-Reply-To: <CD72004A-77C0-4041-8FD6-FF64932138D4@gmail.com>


Deniz Uğur via Xenomai <xenomai@xenomai.org> writes:

> Hello all,
>
> I’m currently trying to run Xenomai on Jetson Xavier (arm64) (base kernel L4T 32.5). I had some successes and fails so far and I wanted to share my progress with you all. Maybe we can find a way to accomplish this experiment.
>
> So far I’ve attempted to build mainline kernel versions 4.19.144, 5.4.72, and 5.7.0. I was only able to boot up 5.7.0 on the Jetson Xavier. I believe this is a good thing because if we can boot up mainline linux then there is a possibility that Xenomai can run as well. On the other hand, NVIDIA supplies us with 4.9.140 and 4.9.210 versions. I have tried to apply 4.9.55 I-pipe patch to 4.9.140 (L4T) and I’ve resolved almost all conflicts. I couldn’t fix entry.S file...
>
> So right now, I’m thinking about two ways to accomplish this experiment. 
> 	- Bump I-pipe 5.4.72 to 5.7.0 and use it as mainline kernel on the target. This could work because Linux 5.7.0 already works without a problem.
> 	- Bump I-pipe 4.9.55 to L4T 4.9.140 and use it as NVIDIA’s forked kernel on the target. If we can solve the conflict on “entry.S” file then maybe this could work as well.
>
> What do you guys think about these solutions?
> Was this matter already tested by any of you?
>
> I’m definitely open to suggestions as I’m not sure if there are any other barriers on this path to run Xenomai on Jetson Xavier.
>

Since v5.7 boots this SoC, then I guess any later kernel release would
do, including v5.10.

If so, then there may be another option, based not on using Xenomai 3.x
on top of the I-pipe, but on top of Dovetail [1] which is the successor
to the I-pipe (the latter is on its way out).

There is a work in progress rebasing Xenomai 3.x on top of Dovetail for
v5.10 [2]. The x86 and aarch32 ports are in a reasonably good shape at the
moment, aarch64 will be available later next week. I'm confident that
the result should be stable enough to experiment with it.

This said, Dovetail (like the I-pipe) never met the Jetson yet (as far
as I know), so there might be a couple of tweaks required. In the
meantime, you could immediately experiment with the EVL core [5], which
is an evolution of Xenomai's Cobalt core, also running on top of
Dovetail. The EVL core will be at the heart of Xenomai 4.x.

The EVL stable tree is based on v5.10 [3]. Any fix we might have to do
there for the Jetson would likely be part of Dovetail, so this could be
seamlessly inherited by [2].

In short, I would suggest to try booting the Jetson with [3] first,
reporting any issue to this list so we can fix them, then wait for [2]
to be available for arm64 in order to experiment with Xenomai, which
should happen fairly soon.

[1] https://evlproject.org/dovetail/
[2] https://lab.xenomai.org/xenomai-rpm.git/log/?h=for-upstream/dovetail
[3] https://git.evlproject.org/linux-evl.git/log/?h=evl/v5.10
[4] https://evlproject.org/core/build-steps/
[5] https://evlproject.org/core/

-- 
Philippe.


  reply	other threads:[~2021-02-21 16:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 18:49 [I-PIPE][ARM64] Experimenting on Jetson Xavier Deniz Uğur
2021-02-21 16:29 ` Philippe Gerum [this message]
2021-02-21 17:35   ` Deniz Uğur
2021-02-21 18:14     ` Philippe Gerum
2021-02-21 21:44       ` Deniz Uğur
2021-02-22  7:01         ` Deniz Uğur
2021-02-22  8:39         ` Philippe Gerum
2021-02-22  9:01           ` Deniz Uğur

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=87a6rx4c6k.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=deniz343@gmail.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.