From: Esben Haabendal <esben@geanix.com>
To: Erez <erezgeva2@gmail.com>
Cc: Michael Walle <mwalle@kernel.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Erez Geva <erezgeva@nwtime.org>,
linux-mtd@lists.infradead.org,
Pratyush Yadav <pratyush@kernel.org>,
linux-kernel@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v5 1/5] mtd: spi-nor: core: add manufacturer flags
Date: Thu, 26 Sep 2024 13:37:06 +0200 [thread overview]
Message-ID: <8734lmhcil.fsf@geanix.com> (raw)
In-Reply-To: <CANeKEMMcZ+Y-f8Kty_4Nk-kRu+F7ZXBbxpAG1Bd_P1vcju1mUA@mail.gmail.com> (Erez's message of "Thu, 26 Sep 2024 13:08:59 +0200")
Erez <erezgeva2@gmail.com> writes:
> On Thu, 26 Sept 2024 at 09:46, Esben Haabendal <esben@geanix.com> wrote:
>>
>> Erez <erezgeva2@gmail.com> writes:
>>
>> > On Mon, 23 Sept 2024 at 18:19, Michael Walle <mwalle@kernel.org> wrote:
>> >>
>> >> > > > I would gladly remove the obsolete mx25l12805d.
>> >> > > Why? I don't see any need for that.
>> >> > Maybe because we do not want compatibility table?
>> >>
>> >> I don't get this? Anyway, we do not remove support for older
>> >> flashes for no reason.
>> >
>> > I did not insist, you asked.
>> > Macronix stopped selling these chips 15 year ago.
>> > How long do you want to support old chips?
>>
>> It is not unusual for embedded products to have a support span of more
>> than 20 years. And chips such as these flashes might not be entirely new
>> when the product is introduced. So dropping support for SPI-NOR flashes
>> that are newer than 25-30 years is definitely a risk. Somebody out there
>> might not be able to upgrade to latest kernel versions anymore, which is
>> not a position we should put anyone in. With the increasing pressure to
>> upgrade product for better security, we definitely should not make it
>> more difficult to run newer kernel versions than absolutely necessary.
>
> I do not insist. Nor send any patch in this direction.
I did not say or imply that you did any such thing.
You asked an open question, and I gave my response. Nothing more,
nothing less.
> Each project can define the extent of backward compatibility.
> In terms of compilers, linkers and tools, i.e. build environment.
> In terms of standards like the C standard we use.
> In terms of network protocols.
> And also what Hardware do we support.
>
> There is no harm in asking where the boundaries are.
> All projects move their boundaries all the time.
> The Linux kernel is no exception.
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Esben Haabendal <esben@geanix.com>
To: Erez <erezgeva2@gmail.com>
Cc: Michael Walle <mwalle@kernel.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Erez Geva <erezgeva@nwtime.org>,
linux-mtd@lists.infradead.org,
Pratyush Yadav <pratyush@kernel.org>,
linux-kernel@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v5 1/5] mtd: spi-nor: core: add manufacturer flags
Date: Thu, 26 Sep 2024 13:37:06 +0200 [thread overview]
Message-ID: <8734lmhcil.fsf@geanix.com> (raw)
In-Reply-To: <CANeKEMMcZ+Y-f8Kty_4Nk-kRu+F7ZXBbxpAG1Bd_P1vcju1mUA@mail.gmail.com> (Erez's message of "Thu, 26 Sep 2024 13:08:59 +0200")
Erez <erezgeva2@gmail.com> writes:
> On Thu, 26 Sept 2024 at 09:46, Esben Haabendal <esben@geanix.com> wrote:
>>
>> Erez <erezgeva2@gmail.com> writes:
>>
>> > On Mon, 23 Sept 2024 at 18:19, Michael Walle <mwalle@kernel.org> wrote:
>> >>
>> >> > > > I would gladly remove the obsolete mx25l12805d.
>> >> > > Why? I don't see any need for that.
>> >> > Maybe because we do not want compatibility table?
>> >>
>> >> I don't get this? Anyway, we do not remove support for older
>> >> flashes for no reason.
>> >
>> > I did not insist, you asked.
>> > Macronix stopped selling these chips 15 year ago.
>> > How long do you want to support old chips?
>>
>> It is not unusual for embedded products to have a support span of more
>> than 20 years. And chips such as these flashes might not be entirely new
>> when the product is introduced. So dropping support for SPI-NOR flashes
>> that are newer than 25-30 years is definitely a risk. Somebody out there
>> might not be able to upgrade to latest kernel versions anymore, which is
>> not a position we should put anyone in. With the increasing pressure to
>> upgrade product for better security, we definitely should not make it
>> more difficult to run newer kernel versions than absolutely necessary.
>
> I do not insist. Nor send any patch in this direction.
I did not say or imply that you did any such thing.
You asked an open question, and I gave my response. Nothing more,
nothing less.
> Each project can define the extent of backward compatibility.
> In terms of compilers, linkers and tools, i.e. build environment.
> In terms of standards like the C standard we use.
> In terms of network protocols.
> And also what Hardware do we support.
>
> There is no harm in asking where the boundaries are.
> All projects move their boundaries all the time.
> The Linux kernel is no exception.
next prev parent reply other threads:[~2024-09-26 11:37 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 18:12 [PATCH v5 0/5] Add support for SPI-NOR Macronix OTP Erez Geva
2024-09-20 18:12 ` Erez Geva
2024-09-20 18:12 ` [PATCH v5 1/5] mtd: spi-nor: core: add manufacturer flags Erez Geva
2024-09-20 18:12 ` Erez Geva
2024-09-23 6:04 ` Tudor Ambarus
2024-09-23 6:04 ` Tudor Ambarus
2024-09-23 10:31 ` Erez
2024-09-23 10:31 ` Erez
2024-09-23 10:46 ` Michael Walle
2024-09-23 10:46 ` Michael Walle
2024-09-23 13:25 ` Erez
2024-09-23 13:25 ` Erez
2024-09-23 16:19 ` Michael Walle
2024-09-23 16:19 ` Michael Walle
2024-09-23 16:31 ` Erez
2024-09-23 16:31 ` Erez
2024-09-23 18:04 ` Tudor Ambarus
2024-09-23 18:04 ` Tudor Ambarus
2024-09-23 18:21 ` Tudor Ambarus
2024-09-23 18:21 ` Tudor Ambarus
2024-09-26 7:46 ` Esben Haabendal
2024-09-26 7:46 ` Esben Haabendal
2024-09-26 11:08 ` Erez
2024-09-26 11:08 ` Erez
2024-09-26 11:37 ` Esben Haabendal [this message]
2024-09-26 11:37 ` Esben Haabendal
2024-09-26 13:16 ` Erez
2024-09-26 13:16 ` Erez
2024-09-23 12:07 ` Tudor Ambarus
2024-09-23 12:07 ` Tudor Ambarus
2024-09-23 13:01 ` Erez
2024-09-23 13:01 ` Erez
2024-09-23 14:18 ` Tudor Ambarus
2024-09-23 14:18 ` Tudor Ambarus
2024-09-23 14:51 ` Erez
2024-09-23 14:51 ` Erez
2024-09-23 17:52 ` Tudor Ambarus
2024-09-23 17:52 ` Tudor Ambarus
2024-09-23 19:30 ` Erez
2024-09-23 19:30 ` Erez
2024-09-23 21:41 ` Erez
2024-09-23 21:41 ` Erez
2024-09-24 6:04 ` Tudor Ambarus
2024-09-24 6:04 ` Tudor Ambarus
2024-09-24 6:01 ` Tudor Ambarus
2024-09-24 6:01 ` Tudor Ambarus
2024-09-20 18:12 ` [PATCH v5 2/5] mtd: spi-nor: core: add generic functions Erez Geva
2024-09-20 18:12 ` Erez Geva
2024-09-20 18:12 ` [PATCH v5 3/5] dt-bindings: mtd: spi-nor: add OTP parameters Erez Geva
2024-09-20 18:12 ` Erez Geva
2024-09-22 20:40 ` Krzysztof Kozlowski
2024-09-22 20:40 ` Krzysztof Kozlowski
2024-09-23 9:21 ` Erez
2024-09-23 9:21 ` Erez
2024-09-23 15:42 ` Krzysztof Kozlowski
2024-09-23 15:42 ` Krzysztof Kozlowski
2024-09-23 15:49 ` Erez
2024-09-23 15:49 ` Erez
2024-09-20 18:12 ` [PATCH v5 4/5] mtd: spi-nor: macronix: add support for OTP Erez Geva
2024-09-20 18:12 ` Erez Geva
2024-09-20 18:12 ` [PATCH v5 5/5] mtd: spi-nor: macronix: add manufacturer flags Erez Geva
2024-09-20 18:12 ` Erez Geva
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=8734lmhcil.fsf@geanix.com \
--to=esben@geanix.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=erezgeva2@gmail.com \
--cc=erezgeva@nwtime.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=vigneshr@ti.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 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.