From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/5] rpi-firmware: bump version to fbad6408c4
Date: Sun, 4 Nov 2018 22:37:16 +0100 [thread overview]
Message-ID: <20181104223716.4625e8a8@gmx.net> (raw)
In-Reply-To: <87efcro3ue.fsf@dell.be.48ers.dk>
Hello PeterK,
On Mon, 15 Oct 2018 13:18:33 +0200, Peter Korsgaard <peter@korsgaard.com> wrote:
> >>>>> "Peter" == Peter Seiderer <ps.report@gmx.net> writes:
>
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> It would be great if you could write some kind of summary of the changes
> when bumping from 1 git revision to another if possible to make it
> easier to judge if any of this should be applied to the 2018.02.x series
> as well, thanks.
>
The rpi firmware short log looks like:
10c1c5f963 kernel: Bump to 4.14.76
fbad6408c4 kernel: Bump to 4.14.74
e924d3e880 kernel: Bump to 4.14.73
e80b826911 kernel: Bump to 4.14.72
[...]
Not very informative, the long log looks like:
commit 45c6ee3cd7f36a2376b691affbc02dfc689b8056 (HEAD -> master, origin/master, origin/HEAD)
Author: popcornmix <popcornmix@gmail.com>
Date: Tue Oct 23 16:16:19 2018 +0100
kernel: Bump to 4.14.78
firmware: Move to driver based backlight
See: https://github.com/raspberrypi/firmware/issues/1063
commit 8993bff0b82f8cd8d60409d28bb61d2197606ebb
Author: popcornmix <popcornmix@gmail.com>
Date: Fri Oct 19 16:17:56 2018 +0100
kernel: Bump to 4.14.77
kernel: Add hy28b 2017 model device tree overlay
See: https://github.com/raspberrypi/linux/pull/2721
commit 10c1c5f9637849e8a3a70e114d3837e25987fc7c
Author: popcornmix <popcornmix@gmail.com>
Date: Mon Oct 15 18:36:13 2018 +0100
kernel: Bump to 4.14.76
kernel: Revert net: pskb_trim_rcsum() and CHECKSUM_COMPLETE are friends
See: https://github.com/raspberrypi/linux/pull/2717
kernel: thermal: add hysteresis support and adjust PoE HAT trip points
See: https://github.com/raspberrypi/linux/pull/2700
kernel: Add composite RPi driver for pcm512x DAC HAT cards
See: https://github.com/raspberrypi/linux/pull/2702
firmware: jpeg/mjpeg: MJPEG doesn't insert JFIF APP0 header
See: https://github.com/raspberrypi/userland/issues/345
firmware: Add IL HVS component
firmware: mmal: Acquire zero copy buffers on being passed to the VPU
firmware: video_render: Use per pixel alpha on RGBA and BGRA
firmware: video_render: Add support for alpha options (MIX and PREMULT)
[...]
Hard to judge what is needed, what is a feature update, what is a security update
and should applied to the long term support buildroot branches....
One solution would be (as long as the rpi kernel updates keep the same major/minor version),
to say this are security updates (as the mainline kernel updates) and try to keep
rpi-userland and rpi-firmware at the same commit level (I can add the referenced kernel version
to the commit log)....
The other solution would be not to backport the rpi updates at all?
Regards,
Peter
next prev parent reply other threads:[~2018-11-04 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 21:09 [Buildroot] [PATCH v1 0/5] Raspberry Pi update Peter Seiderer
2018-10-12 21:09 ` [Buildroot] [PATCH v1 1/5] configs/raspberrypi*: bump kernel version to 6d27aa156c Peter Seiderer
2018-10-12 21:09 ` [Buildroot] [PATCH v1 2/5] rpi-firmware: bump version to fbad6408c4 Peter Seiderer
2018-10-15 11:18 ` Peter Korsgaard
2018-11-04 21:37 ` Peter Seiderer [this message]
2018-10-12 21:09 ` [Buildroot] [PATCH v1 3/5] rpi-userland: bump version to 8f0abfb07b Peter Seiderer
2018-10-12 21:09 ` [Buildroot] [PATCH v1 4/5] rpi-bt-firmware: bump version to 8c1e2bff1d Peter Seiderer
2018-10-12 21:09 ` [Buildroot] [PATCH v1 5/5] rpi-wifi-firmware: " Peter Seiderer
2018-10-15 11:17 ` [Buildroot] [PATCH v1 0/5] Raspberry Pi update Peter Korsgaard
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=20181104223716.4625e8a8@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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