From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ubaldo Porcheddu <ubaldo@eja.it>
Date: Wed, 20 Apr 2016 09:37:45 +0100
Subject: [Buildroot] [PATCH 1/1] Raspberry PI 3 kernel,
	firmware and dtb update
In-Reply-To: <87wpnsdaf2.fsf@dell.be.48ers.dk>
References: <1459421492-18815-1-git-send-email-ubaldo@eja.it>
 <87a8kpe39z.fsf@dell.be.48ers.dk> <20160419213321.GG3505@free.fr>
 <87wpnsdaf2.fsf@dell.be.48ers.dk>
Message-ID: <c8fdfc731bb102efc2b6d3f3d69fc6a0@eja.it>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

Hi,

Il 2016-04-20 08:08 Peter Korsgaard ha scritto:
>>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> 
>  >> The rpi3 afaik uses a different serial port than rpi2. How will 
> that
>  >> work if we use the same defconfig for both boards? Perhaps it makes 
> more
>  >> sense to have a seperate raspberrypi3_defconfig?
> 
>  > Yes, expecially since the CPU is not the same, andthat we may^Wwill 
> one
>  > day have it run in 64-bit mode (one can dream, no?).
> 
> Yeah. I don't know about the rpi foundation, but there seems to be 
> quite
> some aarch64 activity around it in mainline U-Boot/Linux.
> 
> With the recent vc4 work it might make sense to add rpi defconfigs 
> using
> mainline as well?

I am going to submit a patch right now with just the firmware upgrade 
and I will then try a separate rpi3 defconfig to start with.