From: Yixun Lan <dlan@kernel.org>
To: E Shattow <e@freeshell.de>
Cc: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Troy Mitchell <troy.mitchell@linux.spacemit.com>,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: Re: [PATCH 0/2] SpacemiT K3 use 8gb memory size on CoM260 and Pico-ITX
Date: Wed, 18 Nov 2026 07:20:26 +0000 [thread overview]
Message-ID: <20261118072026-GKB156369@kernel.org> (raw)
In-Reply-To: <20261115195112.32120-1-e@freeshell.de>
On 11:50 Sun 15 Nov , E Shattow wrote:
> Adjust from 16GiB to 8GiB memory size configuration on CoM260
> and Pico-ITX for compatibility with 8GiB/16GiB/32GiB configurations.
>
> It is expected that the bootloader will read EEPROM TLV value for
> ID of the EEPROM part and adjust the device tree node accordingly.
> In the simple case where adjustment is not performed however, then
> the previous 16GiB range may overflow a 8GiB DRAM optioned board.
>
> DeepComputing FML13v05 is sold in 16GiB/32GiB variants and not 8GiB
> so it remains as 16GiB configuration.
>
> E Shattow (2):
> riscv: dts: spacemit: k3: use com260 8gb memory configuration
> riscv: dts: spacemit: k3: use pico-itx 8gb memory configuration
>
> arch/riscv/boot/dts/spacemit/k3-com260.dtsi | 2 +-
> arch/riscv/boot/dts/spacemit/k3-pico-itx.dts | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
For the series,
Reviewed-by: Yixun Lan <dlan@kernel.org>
--
Yixun Lan (dlan)
WARNING: multiple messages have this Message-ID (diff)
From: Yixun Lan <dlan@kernel.org>
To: E Shattow <e@freeshell.de>
Cc: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Troy Mitchell <troy.mitchell@linux.spacemit.com>,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: Re: [PATCH 0/2] SpacemiT K3 use 8gb memory size on CoM260 and Pico-ITX
Date: Wed, 18 Nov 2026 07:20:26 +0000 [thread overview]
Message-ID: <20261118072026-GKB156369@kernel.org> (raw)
In-Reply-To: <20261115195112.32120-1-e@freeshell.de>
On 11:50 Sun 15 Nov , E Shattow wrote:
> Adjust from 16GiB to 8GiB memory size configuration on CoM260
> and Pico-ITX for compatibility with 8GiB/16GiB/32GiB configurations.
>
> It is expected that the bootloader will read EEPROM TLV value for
> ID of the EEPROM part and adjust the device tree node accordingly.
> In the simple case where adjustment is not performed however, then
> the previous 16GiB range may overflow a 8GiB DRAM optioned board.
>
> DeepComputing FML13v05 is sold in 16GiB/32GiB variants and not 8GiB
> so it remains as 16GiB configuration.
>
> E Shattow (2):
> riscv: dts: spacemit: k3: use com260 8gb memory configuration
> riscv: dts: spacemit: k3: use pico-itx 8gb memory configuration
>
> arch/riscv/boot/dts/spacemit/k3-com260.dtsi | 2 +-
> arch/riscv/boot/dts/spacemit/k3-pico-itx.dts | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
For the series,
Reviewed-by: Yixun Lan <dlan@kernel.org>
--
Yixun Lan (dlan)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-11-18 7:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 19:50 [PATCH 0/2] SpacemiT K3 use 8gb memory size on CoM260 and Pico-ITX E Shattow
2026-11-15 19:50 ` E Shattow
2026-11-15 19:50 ` [PATCH 1/2] riscv: dts: spacemit: k3: use com260 8gb memory configuration E Shattow
2026-11-15 19:50 ` E Shattow
2026-11-17 0:57 ` Yixun Lan
2026-11-17 0:57 ` Yixun Lan
2026-11-15 19:51 ` [PATCH 2/2] riscv: dts: spacemit: k3: use pico-itx " E Shattow
2026-11-15 19:51 ` E Shattow
2026-11-18 7:20 ` Yixun Lan [this message]
2026-11-18 7:20 ` [PATCH 0/2] SpacemiT K3 use 8gb memory size on CoM260 and Pico-ITX Yixun Lan
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=20261118072026-GKB156369@kernel.org \
--to=dlan@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=e@freeshell.de \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.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 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.