From: Philippe Gerum <rpm@xenomai.org>
To: Hans Petersen <hpetersenlg@googlemail.com>
Cc: xenomai@xenomai.org
Subject: Re: xenomai-4 on raspberry-pi-4
Date: Thu, 19 Aug 2021 15:04:34 +0200 [thread overview]
Message-ID: <87a6ldy49p.fsf@xenomai.org> (raw)
In-Reply-To: <CAHk=vNFHsSE5iaJd30tSxEDiNBD+w2hmuhnY7CD7Rz6EyjqtJg@mail.gmail.com>
Hans Petersen via Xenomai <xenomai@xenomai.org> writes:
> Hi, everyone,
>
> I'm trying to get XENOMAI-4 to run on the Raspberry-PI-4.
>
> For this I downloaded the source files '*v5.10.y-evl-rebase*' and compiled
> them with 'bcm2711_defconfig'.
>
> Unfortunately, the image does not work because many specific files, such as
> the device tree and the broadcom drivers and serveral config-flags, are
> missing in the source tree.
> However, these are also missing in the mainline kernel.
>
Xenomai targets mainline kernels exclusively.
> I can load a kernel version *'5.10.52*' from the *Raspbian repository*.
>
> *Now my question*:
>
> Is there a possibility to patch XENOMAI4 into the Raspbian sources, or any
> other way to install a Xenomai-4 on the Raspberry-PI-4?
>
Unlike its predecessors, Xenomai 4 does not use the patch model, it is
directly developed into the target kernel.
FWIW, I have been running EVL based on the mainline kernel on the rpi4
for more than a year now (headless system though), and this is actually
one of my workhorses for testing it. If you really need to run a vendor
kernel, then you are pretty much on your own unfortunately; you might
try to apply the 5.10.y..5.10.y-evl-rebase diff set to a Raspbian kernel
based on the same mainline version.
--
Philippe.
next prev parent reply other threads:[~2021-08-19 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 12:16 xenomai-4 on raspberry-pi-4 Hans Petersen
2021-08-19 13:04 ` Philippe Gerum [this message]
2021-08-19 17:54 ` Byron Jacquot
2021-08-20 8:11 ` Hans Petersen
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=87a6ldy49p.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=hpetersenlg@googlemail.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.