U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Bee <knaerzche@gmail.com>
To: Tom Rini <trini@konsulko.com>
Cc: Quentin Schulz <foss+uboot@0leil.net>,
	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>,
	u-boot@lists.denx.de, Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [PATCH next 2/2] rockchip: remove support for Theobroma Systems RK3368 Lion
Date: Thu, 20 Jun 2024 19:41:43 +0200	[thread overview]
Message-ID: <d5f90fe2-230d-477b-8d4e-ff6088acebee@gmail.com> (raw)
In-Reply-To: <20240620170830.GQ68077@bill-the-cat>


Am 20.06.24 um 19:08 schrieb Tom Rini:
> On Thu, Jun 20, 2024 at 07:03:26PM +0200, Alex Bee wrote:
>> Am 20.06.24 um 12:24 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.
>> That's a pretty interesting support-strategy. While I really don't care for
>> this board, please don't go ahead and remove the whole TPL-/SPL-part for
>> RK3368 in yet another pointless "cleanup"  only because lion was one the of
>> last/only user. Even if EOL RK3368 is getting finally interesting in
>> regards of display pipeline as we are finally getting a OSS gpu driver [0].
>> I'm planning to add a board which uses TPL/SPL soonish (when my rare spare
>> time allows).
> Please update the MAINTAINERS file for the relevant to your future
> platform, or even better possibly get a skeleton of this platform
> posted. Thanks.
>
I don't think the whole platform would get removed as it has several users
(and is maintained) - I just was a bit worried that TPL/SPL support could
get removed, but now noticed there is one more user: evb-px5. So: sorry for
noise.
So I will go the usual way via upstream DT (linux tree) addition and so
forth.

  reply	other threads:[~2024-06-20 17:41 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
2024-06-20 17:03   ` Alex Bee
2024-06-20 17:08     ` Tom Rini
2024-06-20 17:41       ` Alex Bee [this message]
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=d5f90fe2-230d-477b-8d4e-ff6088acebee@gmail.com \
    --to=knaerzche@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox