From: Leo Liang <ycliang@andestech.com>
To: Jamie Gibbons <jamie.gibbons@microchip.com>
Cc: <u-boot@lists.denx.de>, Conor Dooley <conor.dooley@microchip.com>,
Valentina Fernandez Alanis
<valentina.fernandezalanis@microchip.com>,
"Tom Rini" <trini@konsulko.com>, Rick Chen <rick@andestech.com>,
Yao Zi <ziyao@disroot.org>, Junhui Liu <junhui.liu@pigmoral.tech>,
Cyril Jean <cyril.jean@microchip.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH v2] riscv: Add support for BeagleV-Fire
Date: Mon, 9 Feb 2026 19:20:25 +0800 [thread overview]
Message-ID: <aYnC-TXvQdxtcL2F@swlinux02> (raw)
In-Reply-To: <20260116140830.1422571-1-jamie.gibbons@microchip.com>
On Fri, Jan 16, 2026 at 02:08:30PM +0000, Jamie Gibbons wrote:
> Bring U-Boot support for the BeagleV-Fire by adding a device tree and
> supporting board files etc.
>
> Signed-off-by: Jamie Gibbons <jamie.gibbons@microchip.com>
> ---
> v1 -> v2:
> - add missing configs to defconfig
> - reorder defconfig from `make savedefconfig`
> - add missing implied configs to kconfig for target
> ---
> arch/riscv/Kconfig | 4 +
> board/beagle/beaglev_fire/Kconfig | 43 +++++++++
> board/beagle/beaglev_fire/MAINTAINERS | 7 ++
> board/beagle/beaglev_fire/Makefile | 6 ++
> board/beagle/beaglev_fire/beaglev_fire.c | 117 +++++++++++++++++++++++
> configs/beaglev_fire_defconfig | 29 ++++++
> include/configs/beaglev_fire.h | 57 +++++++++++
> 7 files changed, 263 insertions(+)
> create mode 100644 board/beagle/beaglev_fire/Kconfig
> create mode 100644 board/beagle/beaglev_fire/MAINTAINERS
> create mode 100644 board/beagle/beaglev_fire/Makefile
> create mode 100644 board/beagle/beaglev_fire/beaglev_fire.c
> create mode 100644 configs/beaglev_fire_defconfig
> create mode 100644 include/configs/beaglev_fire.h
Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>
prev parent reply other threads:[~2026-02-09 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 14:08 [PATCH v2] riscv: Add support for BeagleV-Fire Jamie Gibbons
2026-02-09 11:20 ` Leo Liang [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=aYnC-TXvQdxtcL2F@swlinux02 \
--to=ycliang@andestech.com \
--cc=conor.dooley@microchip.com \
--cc=cyril.jean@microchip.com \
--cc=jamie.gibbons@microchip.com \
--cc=jan.kiszka@siemens.com \
--cc=junhui.liu@pigmoral.tech \
--cc=rick@andestech.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=valentina.fernandezalanis@microchip.com \
--cc=ziyao@disroot.org \
/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.