All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: sjg@chromium.org, philipp.tomsich@vrull.eu, kever.yang@rock-chips.com
Cc: trini@konsulko.com, u-boot@lists.denx.de
Subject: Re: [PATCH 00/12] board: qnap-ts433: Cleanups + add support for TS233
Date: Wed, 14 Jan 2026 09:30:17 +0100	[thread overview]
Message-ID: <7897491.nlapOpYt14@diego> (raw)
In-Reply-To: <20260105194723.2928608-1-heiko@sntech.de>

Am Montag, 5. Januar 2026, 20:47:11 Mitteleuropäische Normalzeit schrieb Heiko Stuebner:
> This series does a number of cleanups for the existing TS433 NAS,
> and also introduces support for a second device.
> 
> Right now the code can detect the variant from the I2C eeprom(s) and
> set the fdtfile accordingly. Later on (once I figured out what is needed)
> this should also select an optional overlay, because later model-variants
> do have additional per-disk presence detection and also regulator-handling
> that is not present on the earlier versions.
> 
> Heiko Stuebner (12):
>   rockchip: board: qnap-ts433: Fix TPL binary in build-example
>   rockchip: board: qnap-ts433: drop DW_MMC config options
>   rockchip: board: qnap-ts433: Fix dir naming to allow build-system to
>     find it
>   rockchip: board: qnap-ts433: Update documentation to recent tool
>     versions
>   rockchip: board: qnap-ts433: Add instructions for how to use upstream
>     TF-A
>   rockchip: board: qnap-ts433: Support multiple models of the TSx33
>     family

I've updated the board-ident parsing in v2 to support all the types
of identifiers used in the fielt (there are 3 different types)


Heiko



      parent reply	other threads:[~2026-01-14  8:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05 19:47 [PATCH 00/12] board: qnap-ts433: Cleanups + add support for TS233 Heiko Stuebner
2026-01-05 19:47 ` [PATCH 01/12] rockchip: board: qnap-ts433: Fix TPL binary in build-example Heiko Stuebner
2026-01-05 19:47 ` [PATCH 02/12] rockchip: board: qnap-ts433: drop DW_MMC config options Heiko Stuebner
2026-01-05 19:47 ` [PATCH 03/12] rockchip: board: qnap-ts433: Fix dir naming to allow build-system to find it Heiko Stuebner
2026-01-05 19:47 ` [PATCH 04/12] rockchip: board: qnap-ts433: Update documentation to recent tool versions Heiko Stuebner
2026-01-05 19:47 ` [PATCH 05/12] rockchip: board: qnap-ts433: Add instructions for how to use upstream TF-A Heiko Stuebner
2026-01-05 19:47 ` [PATCH 06/12] rockchip: board: qnap-ts433: Support multiple models of the TSx33 family Heiko Stuebner
2026-01-05 19:47 ` [PATCH 07/12] arm64: dts: rockchip: move cpu_thermal node to the correct position Heiko Stuebner
2026-01-05 19:47 ` [PATCH 08/12] arm64: dts: rockchip: describe mcu eeprom cells on rk3568-ts433 Heiko Stuebner
2026-01-05 19:47 ` [PATCH 09/12] arm64: dts: rockchip: move common qnap tsx33 parts to dtsi Heiko Stuebner
2026-01-05 19:47 ` [PATCH 10/12] arm64: dts: rockchip: add QNAP TS233 devicetree Heiko Stuebner
2026-01-05 19:47 ` [PATCH 11/12] rockchip: board: qnap-ts433: Rename the board code to not be TS433 specific Heiko Stuebner
2026-01-05 19:47 ` [PATCH 12/12] rockchip: board: qnap-tsx33: add support for Qnap TS233 devices Heiko Stuebner
2026-01-14  8:30 ` Heiko Stübner [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=7897491.nlapOpYt14@diego \
    --to=heiko@sntech.de \
    --cc=kever.yang@rock-chips.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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.