netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Stanley-Jones <asj@cban.com>, Rob Braun <bbraun@vix.com>,
	Michael Graff <explorer@vix.com>,
	Matt Thomas <matt@3am-software.com>,
	Arnd Bergmann <arnd@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Is drivers/net/wan/lmc dead?
Date: Tue, 22 Mar 2022 09:14:08 +0100	[thread overview]
Message-ID: <m37d8mieun.fsf@t19.piap.pl> (raw)
In-Reply-To: <20220321144013.440d7fc0@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (Jakub Kicinski's message of "Mon, 21 Mar 2022 14:40:13 -0700")

Jakub Kicinski <kuba@kernel.org> writes:

> It has also received not received a single functional change that'd
> indicate someone owns this HW since the beginning of the git era.
>
> Can we remove this driver or should we invest effort into fixing it?

Ahh, it's where they took a tulip (DEC Ethernet controller) and added
an FPGA/PLD frontend converting Ethernet to/from sync serial (buffering
etc). I guess they were tulip experts and didn't want to mess with PCI
directly.

Alan Cox wrote in 2008 (commit 8ab7b66796):
> Not sure anyone uses this driver any more, maybe we should just drop it ?
> Code is still foul but at least a fraction less broken.

C101, N2 (including hd64570), Cosa, hostess_sv11, Sealevel (including
z85230) are ISA. The last motherboard with ISA slot (just one) I used
was Pentium II + i440LX (or something). Sure, the serial links needed
only obsolete hardware (I had been using an old Pentium ~ 100 MHz router
for years back then). But it was ~ 20 years ago. Are there places on
Earth where such stuff still exists, and uses relatively up-to-date
Linux kernels?

Farsync, LMC, PC300, PCI200SYN and wanXL are PCI. While PCI is obsolete,
I think it's quite possible for such hw to be in active use. wanXL were
expensive (and bit older) cards and thus rare, but PC300 and PCI200SYN
were common at some point (as common as V.35/X.21 etc. stuff could be).
I don't know about Farsync or LMC (though I still have one or two of
the latter, somewhere).

The remaining - fsl_ucc_hdlc, lapbether, slic_ds26522 - are either
embedded drivers (Motorola QUICC engine, Dallas Semi T1/E1/J1 frontend)
or pure software device. QUICC isn't exactly new :-) but it seems to be
referenced by arm64 and PPC DTS files (so this isn't the original
~68020 QUICC).
-- 
Krzysztof "Chris" Hałasa

Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa

  parent reply	other threads:[~2022-03-22  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 21:40 Is drivers/net/wan/lmc dead? Jakub Kicinski
2022-03-21 22:10 ` Arnd Bergmann
2022-03-21 23:06   ` Jakub Kicinski
2022-03-22  8:33     ` Arnd Bergmann
2022-03-22  8:14 ` Krzysztof Hałasa [this message]
2022-03-22  8:54   ` Arnd Bergmann

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=m37d8mieun.fsf@t19.piap.pl \
    --to=khalasa@piap.pl \
    --cc=arnd@kernel.org \
    --cc=asj@cban.com \
    --cc=bbraun@vix.com \
    --cc=explorer@vix.com \
    --cc=kuba@kernel.org \
    --cc=matt@3am-software.com \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).