mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: "Arnd Bergmann" <arnd@arndb.de>, "Heiko Stübner" <heiko@sntech.de>
Cc: Cedric Roux <sed@free.fr>, Russell King <linux@armlinux.org.uk>,
	Linus Walleij <linus.walleij@linaro.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES" 
	<linux-samsung-soc@vger.kernel.org>,
	Olof Johansson <olof@lixom.net>, Kukjin Kim <kgene@kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Sylwester Nawrocki <snawrocki@kernel.org>,
	Tomasz Figa <tomasz.figa@gmail.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Inki Dae <inki.dae@samsung.com>,
	Sam Van Den Berge <sam.van.den.berge@telenet.be>,
	Lihua Yao <ylhuajnu@outlook.com>
Subject: Re: [RFC PATCH] ARM: s3c: mark as deprecated and schedule removal after 2022
Date: Sun, 7 Nov 2021 10:11:43 +0100	[thread overview]
Message-ID: <3ab9583f-de50-e403-955d-89e085d4274a@canonical.com> (raw)
In-Reply-To: <CAK8P3a2Pg8CkXgN8YNhp2U5Kgwf08kQGpLeTsyWKgNpGChC4uQ@mail.gmail.com>

On 06/11/2021 21:13, Arnd Bergmann wrote:
> On Sat, Nov 6, 2021 at 8:33 PM Heiko Stübner <heiko@sntech.de> wrote:
>> Am Samstag, 6. November 2021, 19:20:05 CET schrieb Krzysztof Kozlowski:
>>> On 05/11/2021 18:49, Cedric Roux wrote:
>>>>
>>>> Anyway, there is at least one s3c2440 server on Earth powered
>>>> by the linux kernel. Now you know! :)
>>>
>>> Thanks for coming back! We will see how much of feedback we gather.
>>
>> I do believe all (or at least most) of s3c24xx could run with a devicetree
>> base with core peripherals enabled.
>>
>> So one possible alternative way could be to just deprecate (and then drop)
>> all the board-files + their platform-data parts in mach-s3c.
> 
> Yes, and this would be similar to what we've done for mach-imx and
> mach-omap2 in the past.
> 
> However, I think the Cragganmore/Speyside board that Mark mentioned
> is not in the category of easily converted machines, so leaving only the
> DT-enabled machines around would not help him.
> 
> If this is actually the case, one other possibility would be to remove
> all the board files except for that one, in the hope that the transformation
> (even a partial one) to DT becomes easier when there is no risk of
> breaking other machines.

Dropping board files would be a nice step but only a half-way, because
we could not remove the S3C support from the drivers.

The platform to stay should have either:
1. real users in the production who need updates
or
2. hackers who have hardware, like to play with it and will do the
testing/development.

In the second case (the hackers) having only the hardware but not
testing or running newest kernels does not revive the platform from the
almost-dead stage.


Best regards,
Krzysztof

      reply	other threads:[~2021-11-07  9:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 11:05 Krzysztof Kozlowski
2021-11-02 11:09 ` Krzysztof Kozlowski
2021-11-02 13:05 ` Arnd Bergmann
2021-11-02 14:55   ` Krzysztof Kozlowski
2021-11-02 15:00     ` Krzysztof Kozlowski
2021-11-02 15:36     ` Arnd Bergmann
2021-11-02 16:37 ` Mark Brown
2021-11-03  8:27   ` Krzysztof Kozlowski
2021-11-03 17:05     ` Mark Brown
2021-11-02 17:43 ` Heiko Stübner
2021-11-03  8:34 ` Tomasz Figa
2021-11-05 17:49 ` Cedric Roux
2021-11-06 18:20   ` Krzysztof Kozlowski
2021-11-06 19:33     ` Heiko Stübner
2021-11-06 20:13       ` Arnd Bergmann
2021-11-07  9:11         ` Krzysztof Kozlowski [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=3ab9583f-de50-e403-955d-89e085d4274a@canonical.com \
    --to=krzysztof.kozlowski@canonical.com \
    --cc=arnd@arndb.de \
    --cc=cw00.choi@samsung.com \
    --cc=heiko@sntech.de \
    --cc=inki.dae@samsung.com \
    --cc=kgene@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=olof@lixom.net \
    --cc=sam.van.den.berge@telenet.be \
    --cc=sed@free.fr \
    --cc=snawrocki@kernel.org \
    --cc=tomasz.figa@gmail.com \
    --cc=ylhuajnu@outlook.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®