diff linux-patch/README @ 128:95c2a67e1219

doc, linux-patch: update for failure to mainline DUART28C support
author Mychaela Falconia <falcon@freecalypso.org>
date Tue, 02 Feb 2021 04:32:42 +0000
parents d7a1e7a6d6ba
children b8473892b0ce
line wrap: on
line diff
--- a/linux-patch/README	Fri Jan 29 03:40:20 2021 +0000
+++ b/linux-patch/README	Tue Feb 02 04:32:42 2021 +0000
@@ -18,27 +18,12 @@
 but this patch by itself does not help in any way with DUART28C support.  The
 remaining two patches from the original 2020-09 patch series (a preliminary
 patch fixing an oversight in the quirk interface and then the main patch of
-interest) were met with resistance, however, and the goal of bringing DUART28C
-support into mainline Linux is still in limbo as of 2020-12.
-
-Johan (the ftdi_sio driver maintainer who was the target of our initial pressure
-campaign to get the needed driver quirk accepted) has now proposed a generalized
-version of Mother Mychaela's original idea; this generalized version is just as
-good for our purposes because in the end it still recognizes our custom USB ID
-and sets the quirk flag which we require, but it also helps other potential
-users who may have similar needs, but who work with "any" serial port rather
-than a custom USB ID.  The current version as of this writing of Johan's patch
-series implementing his proposed generalized solution is this one:
-
-https://lore.kernel.org/linux-serial/X8iuCXYhOBVMGvXv@localhost/T/
-
-However, the comments in that thread indicate that the maintainers seem intent
-on delaying this integration until 5.12 merge window if not even later, thus we
-are still months away from any hope of resolution.  Because We The End Users
-cannot be expected to put our lives on hold and just sit and wait for kernel
-maintainers to get their act together, we need some immediate solution for our
-use right now - and the minpatch-* series presented here is our current best
-offering for end user purposes.
+interest) were met with resistance, however - please see the article in
+doc/Linux-DTR-RTS-flaw for the full explanation.  The short version is that
+Linux kernel maintainers are refusing to accept our patch on the basis of their
+assininity, and thus We The End Users will need to apply this patch locally on
+our own systems, probably forever, or at least for the next few billion years
+until the Sun swells into a red giant and engulfs the Earth.
 
 3 end user patch series versions are presented in minpatch-4.4.14,
 minpatch-4.4.240 and minpatch-4.9.240.  4.4.240 and 4.9.240 already include the
@@ -49,9 +34,7 @@
 preliminary patch as well.  After this preliminary patch, each minpatch-*
 version includes the quirk port_probe patch and the main patch adding DUART28C
 support with the needed quirk.  These latter patches are the closest version we
-have to what we are hoping to see eventually merged into mainline, and they have
-already undergone rounds of revision in response to maintainer Johan's criticism
-- but this "minimal patch" version is limited to just the ftdi_sio driver, not
-extending into more generic layers, hence the actual quirk flag is implemented
-inside ftdi_sio, not fully generalized like it is in the version which we are
-hoping to see merged into mainline in future months/years.
+ever got to a mainline-acceptable state: they already underwent rounds of
+revision in response to the maintainer's criticism, addressing and fixing
+various nitpick issues before the whole idea got shot down on more ideological
+grounds.