All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Gherzan <andrei@gherzan.ro>
To: Trevor Woerner <twoerner@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi][PATCH v2] linux-raspberrypi-rt: add
Date: Wed, 18 Jan 2017 16:33:35 +0000	[thread overview]
Message-ID: <20170118163335.GH14533@carbonA> (raw)
In-Reply-To: <CAHUNapTy3KM_MwRkdXVptjUYR5S344pvXKQDG-5v9+==2tA3sQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4227 bytes --]

On Thu, Jan 05, 2017 at 10:54:01PM -0500, Trevor Woerner wrote:
> On Thu, Jan 5, 2017 at 4:59 PM, Paul Barker <paul@paulbarker.me.uk> wrote:
> > On Thu, 5 Jan 2017 15:16:19 -0500
> > Trevor Woerner <twoerner@gmail.com> wrote:
> >
> >> On Thu 2017-01-05 @ 07:33:38 PM, Paul Barker wrote:
> >> > On Thu,  5 Jan 2017 12:42:29 -0500
> >> > Trevor Woerner <twoerner@gmail.com> wrote:
> >> >
> >> > > Add an -rt kernel recipe for Raspberry Pi that includes the FIQ patch which
> >> > > adds stability to the -rt kernel (with full preemption enabled) and is an
> >> > > improvement to simply disabling FIQ on the kernel cmdline.
> >> > >
> >> > > Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> >> > > ---
> >> > >
> >> > > changes since v1:
> >> > >   - use "make savedefconfig" to generate the defconfig instead of just
> >> > >     using the full .config
> >> > >
> >> > >  .../0001-fix-dtbo-rules.patch                      |    44 +
> >> > >  .../FIQ_PREEMPT_RT_on_raspi.patch                  |   310 +
> >> > >  .../linux/linux-raspberrypi-rt-4.4/defconfig       |  1249 +
> >> > >  .../patch-4.4.32-rt43.patch                        | 31403 +++++++++++++++++++
> >> > >  recipes-kernel/linux/linux-raspberrypi-rt_4.4.bb   |    55 +
> >> > >  5 files changed, 33061 insertions(+)
> >> > >  create mode 100644 recipes-kernel/linux/linux-raspberrypi-rt-4.4/0001-fix-dtbo-rules.patch
> >> > >  create mode 100644 recipes-kernel/linux/linux-raspberrypi-rt-4.4/FIQ_PREEMPT_RT_on_raspi.patch
> >> > >  create mode 100644 recipes-kernel/linux/linux-raspberrypi-rt-4.4/defconfig
> >> > >  create mode 100644 recipes-kernel/linux/linux-raspberrypi-rt-4.4/patch-4.4.32-rt43.patch
> >> > >  create mode 100644 recipes-kernel/linux/linux-raspberrypi-rt_4.4.bb
> >> > >
> >> >
> >> > Would it be possible to point SRC_URI at kernel.org [1] instead of
> >> > including the whole patch in meta-raspberrypi? It feels a bit much to
> >> > me to include a >1MB patch file.
> >> >
> >> > [1]: https://www.kernel.org/pub/linux/kernel/projects/rt/4.4/older/patch-4.4.32-rt43.patch.gz
> >>
> >> The "virgin" -rt patch from kernel.org doesn't apply cleanly. First off there
> >> is a slight version mismatch and secondly this is the raspberrypi kernel, not
> >> a pure upstream kernel.
> >>
> >> Is there a way to patch a patch before it gets applied? If it could be
> >> fetched from kernel.org then patched before applying that would be ideal!
> >> The diff isn't that big; it's sad to have to provide a >1MB patch for such
> >> a small tweak. I guess that's why the yocto kernels/patches have their own
> >> repositories on yoctoproject.org?
> >
> > I think it depends how you want to maintain it going forward. With
> > frequent upgrades to linux-raspberrypi I can see that >1MB patch being
> > modified very often and I'm not sure how good it will be for the git
> > repository size and efficiency.
>
> Okay, agreed.
>
> > A linux-raspberrypi-rt repository on GitLab[1] or some other git hosting
> > service may be a good idea. I can see this having value outside the
> > OpenEmbedded/Yocto Project world, especially if the vanilla -rt patches
> > don't directly apply to linux-raspberrypi. If you decide to go this
> > route and need any support to make it happen, let me know and I'll see
> > what I can do.

I vote for a rt repository externally maintained too. Having it here
might not be the best idea on the long term.

>
> Sounds good... and Wow! GitLab looks awesome! I guess I'll look at how
> the yocto kernels are managed and see if it applies.
>

Does it? :)

> > Also, are you thinking of moving the -rt recipe to the 4.9 series when
> > upstream linux-raspberrypi declares that stable?
>
> Yes.
>
> > When they declared 4.4
> > stable they stopped updating the 4.1 series pretty much immediately. I'm
> > currently investigating whether there is any value in maintaining the
> > 4.4 series ourselves after upstream moves on.
>
> I want to see how managing one goes.
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--
Andrei Gherzan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

  reply	other threads:[~2017-01-18 16:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 17:42 [meta-raspberrypi][PATCH v2] linux-raspberrypi-rt: add Trevor Woerner
2017-01-05 19:33 ` Paul Barker
2017-01-05 20:16   ` Trevor Woerner
2017-01-05 21:59     ` Paul Barker
2017-01-06  3:54       ` Trevor Woerner
2017-01-18 16:33         ` Andrei Gherzan [this message]
2017-01-17  0:12       ` Trevor Woerner
2017-01-17  7:51         ` Andreas Müller
2017-01-17  8:14           ` Paul Barker
2017-01-06  4:13 ` Trevor Woerner
2017-01-18 16:23 ` Andrei Gherzan

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=20170118163335.GH14533@carbonA \
    --to=andrei@gherzan.ro \
    --cc=twoerner@gmail.com \
    --cc=yocto@yoctoproject.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.