From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Gero Schwäricke" <gero.schwaericke@posteo.de>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4] configs/cubieboard1: new defconfig
Date: Sat, 13 Jul 2024 22:45:42 +0200 [thread overview]
Message-ID: <20240713224542.537909e5@windsurf> (raw)
In-Reply-To: <20240602214056.619533-1-gero.schwaericke@posteo.de>
On Sun, 2 Jun 2024 21:40:50 +0000
Gero Schwäricke <gero.schwaericke@posteo.de> wrote:
> This patch adds a new defconfig for Cubieboard1 made by Cubietech. It is
> based on the Allwinner A10 SoC. See:
> http://www.cubietech.com/product-detail/cubieboard1.
>
> The defconfig uses upstream U-Boot and Linux.
>
> Signed-off-by: Gero Schwäricke <gero.schwaericke@posteo.de>
> Reviewed-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
> Changes v3 -> v4:
> - reorder defconfig to follow regular options ordering
> - bump kernel from 6.8.11 to 6.8.12 and refresh hashes
> Changes v2 -> v3:
> - bump u-boot and kernel version
> - update kernel dts path (new vendor subdir)
> - update my email address in DEVELOPERS
> - add BR2_DOWNLOAD_FORCE_CHECK_HASHES=y to defconfig
> - add BR2_GLOBAL_PATCH_DIR and custom hashes (utils/add-custom-hashes)
> - minor improvements to readme.txt
> - add link to board details in commit message (requested by Giulio)
> Changes v1 -> v2:
> - fix commit title
> - add entry to DEVELOPERS
> - add board/cubieboard1/readme.txt
> - use extlinux.conf instead of boot.cmd
> ---
> DEVELOPERS | 4 ++
> board/cubietech/cubieboard1/genimage.cfg | 16 +++++++
> .../patches/linux-headers/linux-headers.hash | 1 +
> .../cubieboard1/patches/linux/linux.hash | 2 +
> .../cubieboard1/patches/uboot/uboot.hash | 2 +
> board/cubietech/cubieboard1/readme.txt | 32 ++++++++++++++
> .../boot/extlinux/extlinux.conf | 5 +++
> configs/cubieboard1_defconfig | 42 +++++++++++++++++++
> 8 files changed, 104 insertions(+)
> create mode 100644 board/cubietech/cubieboard1/genimage.cfg
> create mode 120000 board/cubietech/cubieboard1/patches/linux-headers/linux-headers.hash
> create mode 100644 board/cubietech/cubieboard1/patches/linux/linux.hash
> create mode 100644 board/cubietech/cubieboard1/patches/uboot/uboot.hash
> create mode 100644 board/cubietech/cubieboard1/readme.txt
> create mode 100644 board/cubietech/cubieboard1/rootfs_overlay/boot/extlinux/extlinux.conf
> create mode 100644 configs/cubieboard1_defconfig
Sorry for the delay, everything looked good, so I applied your patch.
Thanks for your efforts, and thanks to Giulio for the review!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-13 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 21:40 [Buildroot] [PATCH v4] configs/cubieboard1: new defconfig Gero Schwäricke
2024-07-13 20:45 ` Thomas Petazzoni via buildroot [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=20240713224542.537909e5@windsurf \
--to=buildroot@buildroot.org \
--cc=gero.schwaericke@posteo.de \
--cc=giulio.benetti@benettiengineering.com \
--cc=thomas.petazzoni@bootlin.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