From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12186] Raspberry Pi Zero-W build fails on newer kernel versions
Date: Sat, 14 Sep 2019 12:08:09 +0000 [thread overview]
Message-ID: <bug-12186-163-2Sn0lTrgNZ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12186-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12186
--- Comment #5 from Peter Korsgaard <jacmet@uclibc.org> ---
(In reply to Grzegorz Blach from comment #4)
Ahh, but that is because the kernel version got bumped last week:
commit 42d22f3bdba41da8e6b6ace2c78af2b3e34d7491
Author: Gergely Imreh <imrehg@gmail.com>
Date: Tue Aug 27 15:14:28 2019 +0100
{configs/raspberrypi,package/rpi-firmware}: bump kernel/firmware to
20190819 version
It's the latest original version. The defconfig and
package/rpi-firmware changes are done in a single patch, as they are
going together.
Signed-off-by: Gergely Imreh <imrehg@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Which was applied on the 7th.
I have sent a patch to fix this - And while at it, also change the rpi0
defconfig to use the new dedicated dts file:
https://patchwork.ozlabs.org/patch/1162330/
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-09-14 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 15:40 [Buildroot] [Bug 12186] New: Raspberry Pi Zero-W build fails on newer kernel versions bugzilla at busybox.net
2019-09-04 20:08 ` [Buildroot] [Bug 12186] " bugzilla at busybox.net
2019-09-11 13:33 ` bugzilla at busybox.net
2019-09-12 20:51 ` bugzilla at busybox.net
2019-09-12 20:52 ` bugzilla at busybox.net
2019-09-14 12:08 ` bugzilla at busybox.net [this message]
2019-09-14 12:08 ` bugzilla at busybox.net
2019-09-15 12:55 ` bugzilla at busybox.net
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=bug-12186-163-2Sn0lTrgNZ@https.bugs.busybox.net/ \
--to=bugzilla@busybox.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 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.