From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/7] Add rpi3 b+ support
Date: Sun, 18 Mar 2018 20:07:44 +0100 [thread overview]
Message-ID: <20180318190744.GE2478@scaer> (raw)
In-Reply-To: <CAFGQKxcg_O2Kr-VmUhgiDW9Q_4nZY8ZsMZhLCEcpTg7SZ+un_g@mail.gmail.com>
Martin, All,
On 2018-03-16 21:06 +0000, Martin Bark spake thusly:
> On 16 March 2018 at 19:41, Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> > Hello Martin,
> >
> > On Fri, 16 Mar 2018 18:02:25 +0000, Martin Bark wrote:
> >
> >> Martin Bark (7):
> >> package/rpi-firmware: bump version
> >> configs/raspberrypi*: bump kernel version
> >> board/raspberrypi: add support for rpi3 b+
> >> package/rpi-firmware: improve installation of dtb files
> >> package/rpi-bt-firmware: change to LibreELEC github repo
> >> package/rpi-wifi-firmware: change to LibreELEC github repo
> >> DEVELOPERS: add myself for rpi packages
> >
> > Since you're looking at RPi stuff, could you have a look at
> > http://patchwork.ozlabs.org/patch/779105/, which is sitting in
> > patchwork since quite a while ?
>
> Yes i can look at this.
>
> The only reason for this seems to be the use of the pi3-miniuart-bt
> overlay. Personally i never use this overlay, I set enable_uart=1 in
> config.txt (the same as raspi-config does). Is there a reason
> buildroot favours the pi3-miniuart-bt overlay?
>
> If we switched to using enable_uart=1 there would be no reason to
> include the overlays and no reason for this separate rpi0w defconifg.
I am all iun favour of simplifying and fixing things! Please send a
patch! ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-03-18 19:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 18:02 [Buildroot] [PATCH v3 0/7] Add rpi3 b+ support Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 1/7] package/rpi-firmware: bump version Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 2/7] configs/raspberrypi*: bump kernel version Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 3/7] board/raspberrypi: add support for rpi3 b+ Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 4/7] package/rpi-firmware: improve installation of dtb files Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 5/7] package/rpi-bt-firmware: change to LibreELEC github repo Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 6/7] package/rpi-wifi-firmware: " Martin Bark
2018-03-16 18:02 ` [Buildroot] [PATCH v3 7/7] DEVELOPERS: add myself for rpi packages Martin Bark
2018-03-16 19:41 ` [Buildroot] [PATCH v3 0/7] Add rpi3 b+ support Thomas Petazzoni
2018-03-16 21:06 ` Martin Bark
2018-03-16 22:35 ` Thomas Petazzoni
2018-03-19 17:14 ` Peter Seiderer
2018-03-19 18:18 ` Martin Bark
2018-03-20 12:52 ` Jens Maus
2018-03-22 19:45 ` Martin Bark
2018-03-18 19:07 ` Yann E. MORIN [this message]
2018-03-19 9:38 ` Martin Bark
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=20180318190744.GE2478@scaer \
--to=yann.morin.1998@free.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