From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Sergey Matyukevich <geomatsi@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] configs/orangepi_zero2w: new board
Date: Sun, 5 May 2024 17:44:22 +0200 [thread overview]
Message-ID: <ZjepViPtMWJL05DF@landeda> (raw)
In-Reply-To: <20240505153103.2031941-1-geomatsi@gmail.com>
Sergey, All,
On 2024-05-05 18:30 +0300, Sergey Matyukevich spake thusly:
> This patch adds basic support for the new OrangePi Zero2W board:
> - http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-Zero-2W.html
>
> Brief summary of the board features:
> - H618 Allwinner SoC
> - Quad-Core ARM Cortex-A53 Processor 1.5GHz
> - Mali G31 MP2 GPU
> - LPDDR4: 1GB/2GB/4GB
> - Wi-Fi5.0+BT 5.0
> - 2x Type-C USB 2.0
> - 1x Mini HDMI
> - Wi-Fi 5.0 + BT 5.0
> - 40-pin expansion interface (GPIO / UART / I2C / SPI / PWM)
> - 24-pin expansion interface (2x USB 2.0 / ETH / IR / audio)
>
> BSP includes the following components:
> - mainline ATF v2.10
> - mainline U-Boot v2024.04
> - mainline Linux kernel v6.8
>
> No custom scripts required: all is covered by common orangepi scripts.
>
> Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
> ---
> DEVELOPERS | 1 +
> board/orangepi/orangepi-zero2w/readme.txt | 32 +++++++++++++
> configs/orangepi_zero2w_defconfig | 55 +++++++++++++++++++++++
$ ./utils/docker-run make check-package
configs/orangepi_zero2w_defconfig:0: missing BR2_DOWNLOAD_FORCE_CHECK_HASHES
We're now requiring that defconfig files ensure that all downloads have
their hashes checked, even for cutom versions.
Please see my previous explanations to Francois earlier:
https://lore.kernel.org/buildroot/ZjeDWeQ-Jnutgk0G@landeda/
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-05-05 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 15:30 [Buildroot] [PATCH 1/1] configs/orangepi_zero2w: new board Sergey Matyukevich
2024-05-05 15:44 ` Yann E. MORIN [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=ZjepViPtMWJL05DF@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=geomatsi@gmail.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