From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11111] raspberry pi 3 b+: missing BSP for 64-bit kernel
Date: Mon, 25 Jun 2018 21:15:55 +0000 [thread overview]
Message-ID: <bug-11111-163-DQCji6OELh@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11111-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11111
--- Comment #1 from Peter Seiderer <ps.report@gmx.net> ---
(In reply to nospam+busybox from comment #0)
Did try the raspberrypi3_64_defconfig (on buildroot-git master) on rpi3b (no
plus), did work out of the box with functional login on HDMI and serial
console.
The three changes which are post 2018.5 are:
- configs/raspberrypi*: bump kernel version (from 4.14.29 to 4.15.39), see [1]
- configs/raspberrypi3_64_defconfig: add support for rpi3b+, see [2]
- package/rpi-firmware: bump version, see [3]
[1]
https://git.buildroot.net/buildroot/commit/configs/raspberrypi3_64_defconfig?id=b677b490f7055963ac1f5a15856a6eab904ccbc7
[2]
https://git.buildroot.net/buildroot/commit/configs/raspberrypi3_64_defconfig?id=fbb45f6d7f937e503900a04ff920320c411d8f34
[3]
https://git.buildroot.net/buildroot/commit/package/rpi-firmware?id=975fff568f9b5ea99d02b1c24d434ee4cb490864
So no need for 1. and 2.
Suggestion 3. works (as expected), patch welcome ;-)
Regards,
Peter
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-06-25 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 19:45 [Buildroot] [Bug 11111] New: raspberry pi 3 b+: missing BSP for 64-bit kernel bugzilla at busybox.net
2018-06-25 21:15 ` bugzilla at busybox.net [this message]
2018-06-30 20:07 ` [Buildroot] [Bug 11111] " 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-11111-163-DQCji6OELh@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.