From: Floris Bos <bos@je-eigen-domein.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] raspberrypi2: switch Linux kernel to rpi-3.18.y
Date: Thu, 30 Apr 2015 16:48:47 +0200 [thread overview]
Message-ID: <554240CF.20605@je-eigen-domein.nl> (raw)
In-Reply-To: <1430314604-28680-1-git-send-email-fhunleth@troodon-software.com>
On 04/29/2015 03:36 PM, Frank Hunleth wrote:
> This changes the kernel used on the Raspberry Pi 2 from the 3.19 branch
> back to the 3.18 branch. This provides a couple of advantages:
>
> 1. mmc0 works again. Floris Bos found out that this was due to using
> the precompiled DTB files from rpi-firmware. These DTBs were built
> using 3.18.
> 2. The rpi-3.18.y branch is not regularly rebased like rpi-3.19.y
> according to popcornmix. See
> https://github.com/raspberrypi/linux/issues/915.
>
> Signed-off-by: Frank Hunleth <fhunleth@troodon-software.com>
Can confirm buildroot's raspberrypi2_defconfig now works on a Pi 2
including mmc0, so patch works as intended.
Reviewed-by: Floris Bos <bos@je-eigen-domein.nl>
Did notice the rpi-firmware package itself could use some more work.
Besides the binary device tree files always being installed thing, the
sample config.txt in package/rpi-firmware/config.txt also contains
values that are not that suitable for the Pi 2.
E.g. the Pi 2 normally runs at 900 Mhz but is being downclocked to 700
by "arm_freq=700" there.
Might be better not to have any low level settings like that there, just
"kernel=zImage"
Yours sincerely,
Floris Bos
next prev parent reply other threads:[~2015-04-30 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 13:36 [Buildroot] [PATCH 1/2] raspberrypi2: switch Linux kernel to rpi-3.18.y Frank Hunleth
2015-04-29 13:36 ` [Buildroot] [PATCH 2/2] raspberrypi: bump raspberrypi_dt_defconfig kernel Frank Hunleth
2015-04-30 14:48 ` Floris Bos [this message]
2015-05-01 8:25 ` [Buildroot] [PATCH 1/2] raspberrypi2: switch Linux kernel to rpi-3.18.y Thomas Petazzoni
2015-05-01 10:20 ` Frank Hunleth
2015-05-01 10:46 ` Thomas Petazzoni
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=554240CF.20605@je-eigen-domein.nl \
--to=bos@je-eigen-domein.nl \
--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.