From: "Marcin Niestrój" <m.niestroj@grinn-global.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] board: add Orangepi Zero Plus support
Date: Fri, 06 Nov 2020 19:14:06 +0100 [thread overview]
Message-ID: <87o8ka2w0h.fsf@grinn-global.com> (raw)
In-Reply-To: <87k0v14m7z.fsf@dell.be.48ers.dk>
Peter Korsgaard <peter@korsgaard.com> writes:
>>>>>> "Marcin" == Marcin Niestroj <m.niestroj@grinn-global.com> writes:
>
> > Add initial support for Orangepi Zero Plus board:
> > - U-Boot 2020.10
> > - Linux 5.7.19
> > - Default packages from buildroot
>
> > This patch is based on Orangepi Zero Plus2 board support, so genimage
> > configuration and description is copy pasted. One difference is that
> > newer Linux and U-Boot are selected. Another difference is Ethernet
> > support (Plus) instead of WiFi (Plus2).
>
> > Signed-off-by: Marcin Niestroj <m.niestroj@grinn-global.com>
> > ---
> > changes v1 -> v2:
> > * rebase on Buildroot master
> > * bump U-Boot from 2020.04 to 2020.10
> > * bump Linux from 5.6.6 to 5.7.19
>
> Committed, thanks.
>
> I wonder if we could combine some of all these orangepi defconfigs and
> create a single build that works on multiple boards rather than
> maintaining all these almost similar files?
Both orangepi_zero_plus and orangepi_zero_plus2 use the same
processor. It seems like a good idea to unify them. Maybe next time
someone will want to bump orangepi_zero_plus2 it will be a good occasion
to test both boards with same Linux + U-Boot versions.
--
Marcin Niestr?j
prev parent reply other threads:[~2020-11-06 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 19:53 [Buildroot] [PATCH v2] board: add Orangepi Zero Plus support Marcin Niestroj
2020-11-04 7:25 ` Peter Korsgaard
2020-11-06 18:14 ` Marcin Niestrój [this message]
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=87o8ka2w0h.fsf@grinn-global.com \
--to=m.niestroj@grinn-global.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.