From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] raspberrypi2: switch Linux kernel to rpi-3.18.y
Date: Fri, 1 May 2015 10:25:58 +0200 [thread overview]
Message-ID: <20150501102558.338835cc@free-electrons.com> (raw)
In-Reply-To: <1430314604-28680-1-git-send-email-fhunleth@troodon-software.com>
Dear Frank Hunleth,
On Wed, 29 Apr 2015 09:36:43 -0400, 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>
> ---
> configs/raspberrypi2_defconfig | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Applied both patches, thanks.
What about the raspberrypi_defconfig ? Is there any reason to keep it
around using the 3.12 kernel ? Or can we rename
raspberrypi_dt_defconfig to raspberrypi_defconfig ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-01 8:25 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 ` [Buildroot] [PATCH 1/2] raspberrypi2: switch Linux kernel to rpi-3.18.y Floris Bos
2015-05-01 8:25 ` Thomas Petazzoni [this message]
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=20150501102558.338835cc@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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