linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ahmed S. Darwish" <a.darwish@linutronix.de>
To: "Willett, Tony" <st20214513@outlook.cardiffmet.ac.uk>
Cc: "'linux-rt-users@vger.kernel.org'" <linux-rt-users@vger.kernel.org>
Subject: Re: Problems installing a real time kernel.
Date: Tue, 7 Jun 2022 19:35:20 +0200	[thread overview]
Message-ID: <Yp+MWLaEysfFrqaB@lx-t490> (raw)
In-Reply-To: <CWXP265MB501198E1F104B6044E93E188A5A59@CWXP265MB5011.GBRP265.PROD.OUTLOOK.COM>

On Tue, Jun 07, 2022, Willett, Tony wrote:
> Hello.
>
> I am trying to work with a Franka Emika Panda Robot Arm and to do so I
> need to run a real time kernel on my Linux PC.
>
> This tutorial/walkthrough is my primary source of information-
> https://frankaemika.github.io/docs/installation_linux.html#setting-up-the-real-time-kernel
>

This is not the primary/official documentation. The primary
documentation is at:

    https://wiki.linuxfoundation.org/realtime/preempt_rt_versions

Please clone the linux-stable-rt git repo directly and switch to the
stable rt version you want, instead of manually applying the RT patch.

> Patch the kernel and set up .config file to choose Preemptable kernel (Real-Time).
> Then I compile it, it produces linux-upstream files which I did not expect.
> Making the kernel looked good and then fails with the following error-
> Initially it gives the following warnings-

Vendor patches or instructions cannot be supported here.

Please clone the repository earlier shown, switch to the stable rt
version you need (list of stable rt releases are in the aforementioned
link), mention the tag you've used, then show the exact build command
sequence you did.

Afterwards, hopefully I can provide some further help.

Good luck,

--
Ahmed S. Darwish
Linutronix GmbH

  reply	other threads:[~2022-06-07 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 13:24 Problems installing a real time kernel Willett, Tony
2022-06-07 17:35 ` Ahmed S. Darwish [this message]
2022-06-07 19:47 ` Ralf Mardorf
2022-06-08  8:54   ` Jeremy Jongepier
2022-06-14 10:35 ` Punit Agrawal

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=Yp+MWLaEysfFrqaB@lx-t490 \
    --to=a.darwish@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=st20214513@outlook.cardiffmet.ac.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).