From: "Benoît Mauduit" <bmauduit@beneth.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] configs/raspberrypi3: sync kernel version with rpi/rpi2
Date: Tue, 26 Apr 2016 22:58:21 +0200 [thread overview]
Message-ID: <571FD66D.9050305@beneth.fr> (raw)
In-Reply-To: <20160426213916.241241c7@gmx.net>
Hello all,
On 04/26/2016 09:39 PM, Peter Seiderer wrote:
> Hello Peter, Oscar,
>
> On Tue, 26 Apr 2016 19:51:46 +0200, Peter Korsgaard <peter@korsgaard.com> wrote:
>
>>>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>
>>>>>>> "Oscar" == Oscar Gomez Fuente <oscargomezf@gmail.com> writes:
>> >> Hi Peter,
>> >> The following models have been checked on a custom buildroot branch of mine
>> >> (with a few changes), but it's based on the Latest stable release of
>> >> buildroot: 2016.02 and before executing a defconfig I executed a make clean
>>
>> >> I've changed:
>> >> BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="3de232825c9ba5989522b8691eb6ac5df6619458"
>> >> BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
>>
>> > Ok, can you please try current git to make sure? We've also updated the
>> > version of rpi-firmware since 2016.02, so that might make a difference.
>>
>> FYI, I've built the 3 defconfigs using current git head (except that I
>> used precompiled toolchains) and put them online here for easy testing:
>>
>> https://buildroot.org/~jacmet/rpi/
>>
>> Just dd the sdcard.img matching your board variant to a sdcard. I've
>> verified the rpi1 version here.
>>
>
>
> https://buildroot.org/~jacmet/rpi/rpi1/sdcard.img
> Boots fine on a Raspberry Pi Model B Rev 2 board (console on HDMI and serial)
>
> https://buildroot.org/~jacmet/rpi/rpi3/sdcard.img
> Boots fine on a Raspberry Pi 3 Model B Rev 1.2 (messages on HDMI,
> console on HDMI and serial after adding the 'dtoverlay=pi3-disable-bt' fix).
>
For information, I have successfully built a working Linux kernel for
rpi2 on top of the branch rpi-4.4.y.
BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="e63db5f23b77ba5e2fa7823e9b3254bb65358b69"
Do you think we can move to this branch ?
Thanks,
Beno?t.
> Regards,
> Peter
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Beno?t Mauduit
<bmauduit@beneth.fr>
XMPP (Jabber) : <bmauduit@im.beneth.fr>
next prev parent reply other threads:[~2016-04-26 20:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 14:27 [Buildroot] [git commit] configs/raspberrypi3: sync kernel version with rpi/rpi2 Oscar Gomez Fuente
2016-04-26 14:38 ` Peter Korsgaard
2016-04-26 15:09 ` Oscar Gomez Fuente
2016-04-26 15:30 ` Peter Korsgaard
2016-04-26 17:51 ` Peter Korsgaard
2016-04-26 19:39 ` Peter Seiderer
2016-04-26 20:58 ` Benoît Mauduit [this message]
2016-04-27 20:40 ` Peter Korsgaard
2016-04-27 21:16 ` Benoît Mauduit
2016-04-27 21:37 ` Peter Korsgaard
2016-04-27 6:50 ` Peter Korsgaard
2016-04-27 8:24 ` Peter Seiderer
2016-04-27 11:47 ` Oscar Gomez Fuente
2016-04-28 6:53 ` Peter Korsgaard
2016-04-27 6:58 ` Oscar Gomez Fuente
2016-04-27 7:28 ` Oscar Gomez Fuente
2016-04-27 8:19 ` Peter Seiderer
2016-04-27 8:14 ` Peter Seiderer
-- strict thread matches above, loose matches on Subject: below --
2016-04-25 12:07 Peter Korsgaard
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=571FD66D.9050305@beneth.fr \
--to=bmauduit@beneth.fr \
--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