linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Giuliano Colla <giuliano.colla@fastwebnet.it>
To: linux-rt-users@vger.kernel.org
Subject: RT_PREEMPT on Raspberry PI 3
Date: Sun, 18 Sep 2016 12:03:42 +0200	[thread overview]
Message-ID: <2c0e540f-c501-f65b-1292-782e12f71039@fastwebnet.it> (raw)

Hi everybody,

I'm developing industrial applications requiring real-time performance 
on a Raspberry pi3 platform.

I have managed to achieve both good performance and good stability, but 
I have been obliged to overcome some difficulties which IMHO could have 
been avoided if the Raspberry platform peculiarities had been given more 
attention. Being a very popular platform, particularly suited also for 
real-time applications, I believe it deserves it.

The main items are:

1) The RT patches are not in sync with mainline Raspbian kernel 
versions. At the time of writing, the stock 4.x kernel supported is 
4.4.21, while the last available patch is 4.4.19-rt27. Even going 
backwards it's impossible to find a perfect match: 4.4.14 against 
4.4.12-rt20 or 4.4.15-rt23, and so on.

I'm currently using a 4.4.13 kernel with a 4.4.12-rt19 patch, which was 
the best match I could find, and which required some minor manual 
adjustments.

Is there a way to provide a better sync?

2) The RT_PREEMPT patch is not compatible with FIQ (or maybe FIQ is not 
compatible with RT_PREEMPT). Leaving FIQ enabled generates intolerably 
frequent freezes. It appears to work properly only on the basic 
Raspberry pi (single core) but not on the multicore Pi2 and Pi3. 
Currently the only way to make a real-time kernel run on Raspberry PI 2 
or 3 is to disable FIQ on the command line.

If the RT_PREEMPT patch could somehow support this incompatibility 
(either by fully disabling FIQ or fixing the code) this would be a great 
help, thus avoiding populating forums with "my raspberry pi2/3 freezes 
with rt patch"

Can something be done to solve those issues?

Thanks,

Giuliano



             reply	other threads:[~2016-09-18 10:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-18 10:03 Giuliano Colla [this message]
2016-09-22 14:10 ` RT_PREEMPT on Raspberry PI 3 Sebastian Andrzej Siewior
2016-11-18 10:25   ` Oussama Ghorbel
2016-11-18 14:21     ` Jeff Epler
2016-11-28 15:59     ` Sebastian Andrzej Siewior
2016-11-29 15:24       ` Oussama Ghorbel
2016-12-01 15:16         ` Sebastian Andrzej Siewior
2016-12-01 16:24           ` Oussama Ghorbel
2016-12-01  2:11     ` Trevor Woerner
2016-12-01  2:25 ` Trevor Woerner

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=2c0e540f-c501-f65b-1292-782e12f71039@fastwebnet.it \
    --to=giuliano.colla@fastwebnet.it \
    --cc=linux-rt-users@vger.kernel.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 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).