lkml.org 
[lkml]   [2021]   [Jan]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectNew platforms: bring out your dead, was Re: Old platforms: bring out your dead
On Wed, 13 Jan 2021, Arnd Bergmann wrote:

>
> It's usually one of two things that happened before a platform gets
> deleted for good:
>
> * The platform port was (almost) exclusively done by one company
> with a commercial interest in it, and the company shifts its priorities
> for some reason (acquisition, bankruptcy, product cancellation,
> accidentally laying off all competent developers, ...) that causes it to
> stop working on it. Sometimes the previously paid maintainers
> keep up their upstream position, but without someone pushing the
> last missing bits into an official release, users are stuck on an old
> BSP kernel.
>

Yes, that's the typical product life cycle. It presumes a short window of
opportunity for sales (suggesting that demand is not organic).

Most vendors like to avoid having to compete with their own prior product
lines. Hence the constrained lifespan that we get from devices with
out-of-tree Linux ports.

AFAICS open source licenses cannot really prevent this (no matter how many
freedoms the FSF would like to confer on people). However, consumer law
could do it, if it were to disallow products which were not servicable.

> * A platform port is done in the open and actually works for upstream
> users, but over time the last active maintainers move on in their
> lives. Complex platforms inevitably break when a treewide change
> goes wrong, so we rely on users that are able to bisect and report
> bugs when they happen.

And without bug reports, breakage gets leveraged into deletion, using the
bogus argument that "broken" code is proof of zero potential users.

> After a platform has been broken for too long, even competent users
> may decide to just give up and stay on their last working kernel. Some
> of these platforms eventually recover when a new maintainer steps up
> or someone discovers they depend on newer kernels for products, but
> after a few years it's usually beyond repair.
>

So all a vendor has to do is make maintenance a bit too difficult for
competent users e.g. by depriving them of access to existing
documentation.

It was only a few decades ago that every applicance you bought came with a
printed circuit schematic. These days, every device you buy comes with
built-in obsolescence and a customer lock-in strategy.

> Arnd
>

\
 
 \ /
  Last update: 2021-01-14 04:57    [W:0.772 / U:0.132 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site