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: Wed, 11 Sep 2019 13:33:13 +0000 [thread overview]
Message-ID: <bug-12186-163-KiW99zw45C@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12186-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12186
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Unless I'm mistaken, there is no bug. Our current RPi0w defconfig works fine,
and it's only when you change it to use a different kernel version that it no
longer builds. But this is obviously not a bug: if you tweak a part of a
defconfig, you may need to also adjust other parts of that defconfig. In this
specific example, if newer versions of the kernel have renamed the Device Tree
for the platform, obviously the list of Device Trees that Buildroot will
build/install should be updated accordingly.
Of course, let me know if I misunderstood. Don't hesitate to reopen the bug in
such a case.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-09-11 13:33 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 [this message]
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
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-KiW99zw45C@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox