* Status of orphaned ltq_etop ethernet driver: mainline vs. OpenWRT
@ 2026-01-28 20:23 Heiner Kallweit
2026-01-29 0:04 ` Hauke Mehrtens
0 siblings, 1 reply; 4+ messages in thread
From: Heiner Kallweit @ 2026-01-28 20:23 UTC (permalink / raw)
To: John Crispin, Ralph Hempel, John Crispin, Hauke Mehrtens,
Daniel Golle, Jakub Kicinski, Paolo Abeni, Eric Dumazet,
David Miller, Andrew Lunn
Cc: netdev@vger.kernel.org
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?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Status of orphaned ltq_etop ethernet driver: mainline vs. OpenWRT
2026-01-28 20:23 Status of orphaned ltq_etop ethernet driver: mainline vs. OpenWRT Heiner Kallweit
@ 2026-01-29 0:04 ` Hauke Mehrtens
2026-01-29 17:19 ` Heiner Kallweit
2026-01-30 0:07 ` Rosen Penev
0 siblings, 2 replies; 4+ messages in thread
From: Hauke Mehrtens @ 2026-01-29 0:04 UTC (permalink / raw)
To: Heiner Kallweit, John Crispin, Daniel Golle, Jakub Kicinski,
Paolo Abeni, Eric Dumazet, David Miller, Andrew Lunn
Cc: netdev@vger.kernel.org, OpenWrt Development List
On 1/28/26 21:23, Heiner Kallweit wrote:
> 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?
>
Hi,
I think dropping this from the mainline kernel is fine, if it causes
efforts for you.
This is the Ethernet of the Lantiq Danube SoC, the SoC is probably EoL
since 15 years. I assume that all users either use the vendor SDK with
Linux 2.6.X or OpenWrt.
I will not spend much effort on this driver and others will probably
also not spend much effort. We can move it completely into OpenWrt and
keep it running there.
Hauke
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Status of orphaned ltq_etop ethernet driver: mainline vs. OpenWRT
2026-01-29 0:04 ` Hauke Mehrtens
@ 2026-01-29 17:19 ` Heiner Kallweit
2026-01-30 0:07 ` Rosen Penev
1 sibling, 0 replies; 4+ messages in thread
From: Heiner Kallweit @ 2026-01-29 17:19 UTC (permalink / raw)
To: Hauke Mehrtens, John Crispin, Daniel Golle, Jakub Kicinski,
Paolo Abeni, Eric Dumazet, David Miller, Andrew Lunn
Cc: netdev@vger.kernel.org, OpenWrt Development List
On 1/29/2026 1:04 AM, Hauke Mehrtens wrote:
> On 1/28/26 21:23, Heiner Kallweit wrote:
>> 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?
>>
>
> Hi,
>
> I think dropping this from the mainline kernel is fine, if it causes efforts for you.
> This is the Ethernet of the Lantiq Danube SoC, the SoC is probably EoL since 15 years. I assume that all users either use the vendor SDK with Linux 2.6.X or OpenWrt.
>
> I will not spend much effort on this driver and others will probably also not spend much effort. We can move it completely into OpenWrt and keep it running there.
>
Great, thanks for the prompt reply. Then I'll submit a patch for
removing this driver from mainline.
> Hauke
Heiner
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Status of orphaned ltq_etop ethernet driver: mainline vs. OpenWRT
2026-01-29 0:04 ` Hauke Mehrtens
2026-01-29 17:19 ` Heiner Kallweit
@ 2026-01-30 0:07 ` Rosen Penev
1 sibling, 0 replies; 4+ messages in thread
From: Rosen Penev @ 2026-01-30 0:07 UTC (permalink / raw)
To: Hauke Mehrtens
Cc: Heiner Kallweit, John Crispin, Daniel Golle, Jakub Kicinski,
Paolo Abeni, Eric Dumazet, David Miller, Andrew Lunn,
netdev@vger.kernel.org, OpenWrt Development List
On Thu, Jan 29, 2026 at 12:36 PM Hauke Mehrtens <hauke@hauke-m.de> wrote:
>
> On 1/28/26 21:23, Heiner Kallweit wrote:
> > 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?
> >
>
> Hi,
>
> I think dropping this from the mainline kernel is fine, if it causes
> efforts for you.
> This is the Ethernet of the Lantiq Danube SoC, the SoC is probably EoL
> since 15 years. I assume that all users either use the vendor SDK with
> Linux 2.6.X or OpenWrt.
>
> I will not spend much effort on this driver and others will probably
> also not spend much effort. We can move it completely into OpenWrt and
> keep it running there.
FWIW I have some cleanup commits on the driver. Would be great to have
the driver as C files to make editing easier...
>
> Hauke
>
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-01-30 0:07 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-01-28 20:23 Status of orphaned ltq_etop ethernet driver: mainline vs. OpenWRT Heiner Kallweit
2026-01-29 0:04 ` Hauke Mehrtens
2026-01-29 17:19 ` Heiner Kallweit
2026-01-30 0:07 ` Rosen Penev
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox