Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Marcin Niestroj <m.niestroj@grinn-global.com>
Cc: Sergey Kuzminov <kuzminov.sergey81@gmail.com>,
	Sergey Matyukevich <geomatsi@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] board: add Orangepi Zero3 support
Date: Sat, 30 Sep 2023 17:31:46 +0200	[thread overview]
Message-ID: <87a5t3ad99.fsf@48ers.dk> (raw)
In-Reply-To: <20230918064711.1379428-1-m.niestroj@grinn-global.com> (Marcin Niestroj's message of "Mon, 18 Sep 2023 08:47:11 +0200")

>>>>> "Marcin" == Marcin Niestroj <m.niestroj@grinn-global.com> writes:

 > Add initial support for Orangepi Zero3 board:
 > - U-Boot 2021.07 fork by Orangepi
 > - Linux 6.1.31 fork by Orangepi
 > - Default packages from buildroot

 > Enable CONFIG_MFD_AC200 as it is used directly by other module,
 > resulting in build failure when disabled.

 > Signed-off-by: Marcin Niestroj <m.niestroj@grinn-global.com>
 > ---
 > v1 -> v2:
 >  * use 'linux_sunxi64' instead of default arch defconfig, which fixes
 >    ethernet networking (suggested by Sergey)
 >  * disabled rootfs.tar generation (suggested by Sergey)
 >  * increased ext2 fs size to 180M to fit more kernel modules
 >  * added DEVELOPERS entries for board files

Committed, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-09-30 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  6:47 [Buildroot] [PATCH v2] board: add Orangepi Zero3 support Marcin Niestroj
2023-09-26 16:37 ` Sergey Kuzminov
2023-09-30 15:31 ` Peter Korsgaard [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=87a5t3ad99.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=geomatsi@gmail.com \
    --cc=kuzminov.sergey81@gmail.com \
    --cc=m.niestroj@grinn-global.com \
    /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