From: "Heiko Stübner" <heiko@sntech.de>
To: Klaus Goger <klaus.goger@cherry.de>,
Heiko Stuebner <heiko.stuebner@cherry.de>,
Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>,
Tom Rini <trini@konsulko.com>,
u-boot@lists.denx.de
Cc: u-boot@lists.denx.de, Quentin Schulz <quentin.schulz@cherry.de>,
Quentin Schulz <foss+uboot@0leil.net>
Subject: Re: [PATCH next 2/2] rockchip: remove support for Theobroma Systems RK3368 Lion
Date: Thu, 20 Jun 2024 12:52:38 +0200 [thread overview]
Message-ID: <10173419.L8ug28u51p@diego> (raw)
In-Reply-To: <20240620-tsd-http-git-clone-v1-2-666e8d6a8949@cherry.de>
Am Donnerstag, 20. Juni 2024, 12:24:51 CEST schrieb Quentin Schulz:
> From: Quentin Schulz <quentin.schulz@cherry.de>
>
> No meaningful changes were made to this SoM since February 2021. Nobody
> from Theobroma has booted anything recent on that product since July
> 2021 at the latest. The product isn't available to buy anymore and
> disappeared from our website.
>
> This product is therefore unmaintained and it would be disingenuous to
> say the opposite, so drop support for RK3368 Lion.
>
> If you're a user of Lion, feel free to revert this patch or contact our
> sales/support department.
>
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
I think any meaningful work on rk3368 in general has pretty much stalled
at this point.
Acked-by: Heiko Stuebner <heiko@sntech.de>
next prev parent reply other threads:[~2024-06-20 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 10:24 [PATCH next 0/2] rockchip: theobroma: use HTTPS for git URLs and drop RK3368 Lion support Quentin Schulz
2024-06-20 10:24 ` [PATCH next 1/2] rockchip: theobroma-systems: migrate git URLs to HTTPS Quentin Schulz
2024-07-16 2:17 ` Kever Yang
2024-06-20 10:24 ` [PATCH next 2/2] rockchip: remove support for Theobroma Systems RK3368 Lion Quentin Schulz
2024-06-20 10:52 ` Heiko Stübner [this message]
2024-06-20 17:03 ` Alex Bee
2024-06-20 17:08 ` Tom Rini
2024-06-20 17:41 ` Alex Bee
2024-06-20 17:53 ` Peter Robinson
2024-07-16 2:17 ` Kever Yang
2024-07-17 6:47 ` Kever Yang
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=10173419.L8ug28u51p@diego \
--to=heiko@sntech.de \
--cc=foss+uboot@0leil.net \
--cc=heiko.stuebner@cherry.de \
--cc=kever.yang@rock-chips.com \
--cc=klaus.goger@cherry.de \
--cc=philipp.tomsich@vrull.eu \
--cc=quentin.schulz@cherry.de \
--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.