From: Yixun Lan <dlan@kernel.org>
To: Hung-Chun Tseng <alan.tseng.cs@gmail.com>
Cc: Huan Zhou <pericycle.cc@gmail.com>,
Eric Chung <eric.chung@riscstar.com>,
Tom Rini <trini@konsulko.com>, Guodong Xu <docular.xu@gmail.com>,
Raymond Mao <raymond.mao@riscstar.com>,
u-boot-spacemit@groups.io, u-boot@lists.u-boot-project.org
Subject: Re: [PATCH 0/2] spacemit: k1: two small fixes found on a Milk-V Jupiter
Date: Tue, 27 Oct 2026 21:48:36 +0000 [thread overview]
Message-ID: <20261027214836-GKE125937@kernel.org> (raw)
In-Reply-To: <20261027154347.1392094-1-alan.tseng.cs@gmail.com>
Hi Hung-Chun,
On 23:43 Tue 27 Oct , Hung-Chun Tseng wrote:
> Two small fixes I ran into while booting the mainline SPL and U-Boot
> from an SD card on a Milk-V Jupiter.
>
> Patch 1 enables the GigaDevice SPI NOR ID table, which the Jupiter's
> GD25Q64 needs; "sf probe" detects it on the board with the patch.
>
> Patch 2 initialises the EEPROM index that read_ddr_info() passes to
> read_tlvinfo_tlv_eeprom(). It is build-tested only; on the Jupiter the
> current compiler happens to pass 0 already, and the DDR TLV fields are
> read correctly.
>
> Hung-Chun Tseng (2):
> configs: k1: enable GigaDevice SPI NOR flash support
> spacemit: k1: initialise the EEPROM index in read_ddr_info()
>
> board/spacemit/k1/spl.c | 2 +-
> configs/spacemit_k1_defconfig | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
for the series, with
Reviewed-by: Yixun Lan <dlan@kernel.org>
--
Yixun Lan (dlan)
prev parent reply other threads:[~2026-10-27 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 15:43 [PATCH 0/2] spacemit: k1: two small fixes found on a Milk-V Jupiter Hung-Chun Tseng
2026-10-27 15:43 ` [PATCH 1/2] configs: k1: enable GigaDevice SPI NOR flash support Hung-Chun Tseng
2026-10-27 17:54 ` E Shattow
2026-10-27 15:43 ` [PATCH 2/2] spacemit: k1: initialise the EEPROM index in read_ddr_info() Hung-Chun Tseng
2026-10-27 17:55 ` E Shattow
2026-10-27 21:48 ` Yixun Lan [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=20261027214836-GKE125937@kernel.org \
--to=dlan@kernel.org \
--cc=alan.tseng.cs@gmail.com \
--cc=docular.xu@gmail.com \
--cc=eric.chung@riscstar.com \
--cc=pericycle.cc@gmail.com \
--cc=raymond.mao@riscstar.com \
--cc=trini@konsulko.com \
--cc=u-boot-spacemit@groups.io \
--cc=u-boot@lists.u-boot-project.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.