From: Ubaldo Porcheddu <ubaldo@eja.it>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Raspberry PI 3 kernel, firmware and dtb update
Date: Wed, 20 Apr 2016 09:37:45 +0100 [thread overview]
Message-ID: <c8fdfc731bb102efc2b6d3f3d69fc6a0@eja.it> (raw)
In-Reply-To: <87wpnsdaf2.fsf@dell.be.48ers.dk>
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.
next prev parent reply other threads:[~2016-04-20 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 10:51 [Buildroot] [PATCH 1/1] Raspberry PI 3 kernel, firmware and dtb update Ubaldo Porcheddu
2016-04-19 20:45 ` Peter Korsgaard
2016-04-19 21:33 ` Yann E. MORIN
2016-04-20 7:08 ` Peter Korsgaard
2016-04-20 8:37 ` Ubaldo Porcheddu [this message]
2016-04-20 14:25 ` Gustavo Zacarias
2016-04-23 8:36 ` Peter Korsgaard
2016-04-23 16:53 ` Yann E. MORIN
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=c8fdfc731bb102efc2b6d3f3d69fc6a0@eja.it \
--to=ubaldo@eja.it \
--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