linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: linux-rt-users@vger.kernel.org
Cc: Gene Heskett <gheskett@shentel.net>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] 4.19.72-rt25
Date: Wed, 09 Oct 2019 09:23:49 +0200	[thread overview]
Message-ID: <74795460.9uHKpU0Xat@ada> (raw)
In-Reply-To: <201910071516.04269.gheskett@shentel.net>

Hello Gene,

Am Montag, 7. Oktober 2019, 15:16:04 CEST schrieb Gene Heskett:
> On Monday 07 October 2019 15:10:05 Gene Heskett wrote:
> > Unfortunately, this does not work for the pi3-4 family. When its all
> > pulled in and patched, there is no arch/arm/configs bcm2709_defconfig
> > or bcm2711_defconfig for either a pi3b or the new pi4b.
> > 
> > I'll go find the 5.2.14 announce and see if its any more complete.
> 
> Its disappeared.

Not quite. Those were never (?) there. ;-)

You'll find those files in the raspberrypi tree [1], but not in mainline. 

It is possible to run a vanilla kernel on RPi 1 to 3, I guess the 
'multi_v7_defconfig' is a good start for 2 and 3. (This works, I have a 
running RPi 3 with unpatched mainline kernel on my desk, without RT however.)

IIRC from linux-arm-kernel list, basic support for RPi 4 is still under review 
and not yet present in mainline?

So you could try a RPi 2 or 3 with mainline + RT or you try to apply the RT 
patches to the vendor/raspberry tree, but I would not count on anyone 
supporting the latter.

HTH & Greets
Alex

[1] https://github.com/raspberrypi/linux


  reply	other threads:[~2019-10-09  7:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 21:39 [ANNOUNCE] 4.19.72-rt25 Steven Rostedt
2019-10-07 19:10 ` Gene Heskett
2019-10-07 19:16   ` Gene Heskett
2019-10-09  7:23     ` Alexander Dahl [this message]
2019-10-09 10:21       ` Gene Heskett

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=74795460.9uHKpU0Xat@ada \
    --to=ada@thorsis.com \
    --cc=gheskett@shentel.net \
    --cc=linux-kernel@vger.kernel.org \
    --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).