From: Heiner Kallweit <hkallweit1@gmail.com>
To: John Crispin <blogic@openwrt.org>,
Ralph Hempel <ralph.hempel@lantiq.com>,
John Crispin <john@phrozen.org>,
Hauke Mehrtens <hauke@hauke-m.de>,
Daniel Golle <daniel@makrotopia.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
David Miller <davem@davemloft.net>,
Andrew Lunn <andrew+netdev@lunn.ch>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Status of orphaned ltq_etop ethernet driver: mainline vs. OpenWRT
Date: Wed, 28 Jan 2026 21:23:05 +0100 [thread overview]
Message-ID: <43dff7cf-cb00-4480-8856-501a8313951e@gmail.com> (raw)
This driver in mainline lost its in-tree user with commit
cd93b4895ea5 ("MIPS: lantiq: drop mips_machine support")
in 2012. Since then it has had no in-tree user.
Only (?) user seems to be OpenWRT, with several changes to
the in-tree driver version:
target/linux/lantiq/patches-6.12/035-owrt-lantiq-wifi-and-ethernet-eeprom-handling.patch
target/linux/lantiq/patches-6.12/028-NET-lantiq-various-etop-fixes.patch
target/linux/lantiq/patches-6.12/701-NET-lantiq-etop-of-mido.patch
So it seems the driver is maintained in OpenWrt only
(except tree-wide in-tree changes).
To me this leaves two questions:
- Move this driver to OpenWRT completely?
- Or mainline all downstream changes, maintain driver in
mainline, and mainline also the users of this driver?
next reply other threads:[~2026-01-28 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 20:23 Heiner Kallweit [this message]
2026-01-29 0:04 ` Status of orphaned ltq_etop ethernet driver: mainline vs. OpenWRT Hauke Mehrtens
2026-01-29 17:19 ` Heiner Kallweit
2026-01-30 0:07 ` Rosen Penev
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=43dff7cf-cb00-4480-8856-501a8313951e@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=blogic@openwrt.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hauke@hauke-m.de \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ralph.hempel@lantiq.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