LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: Cai Huoqing <caihuoqing@baidu.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Jason Gunthorpe <jgg@ziepe.ca>, netdev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] net: ethernet: Remove the 8390 network drivers
Date: Mon, 9 Aug 2021 13:57:24 +0200 [thread overview]
Message-ID: <CAMuHMdXzZfX_mZe==-J52kaUCuM0t-zvFw5aqJTgy8TKJ9Xmvw@mail.gmail.com> (raw)
In-Reply-To: <05a5ddb5-1c51-8679-60a3-a74e0688b72d@gmail.com>
On Sun, Aug 8, 2021 at 12:50 AM Michael Schmitz <schmitzmic@gmail.com> wrote:
> a number of the 8390 drivers are still in active use on legacy
> architectures. These drivers get occasional updates (not just bugfixes,
Exactly.
> but support for 'new' network cards - I have a patch to add X-Surf 500
> support somewhere in the pipline).
According to the picture on [1], the X-Surf 500 is from 2018.
The ASIX AX88796B[2] it is based on seems to be readily available,
so new designs may still use the "obsolete" 8390.
[1] https://icomp.de/shop-icomp/en/produkt-details/product/x-surf-500.html
[2] https://www.asix.com.tw/en/product/EmbeddedEthernet/1-Port_Ethernet/AX88796B
> Am 08.08.2021 um 02:56 schrieb Cai Huoqing:
> > commit <0cf445ceaf43> ("<netdev: Update status of 8390 based drivers>")
> > indicated the 8390 network drivers as orphan/obsolete in Jan 2011,
> > updated in the MAINTAINERS file.
> >
> > now, after being exposed for 10 years to refactoring and
> > no one has become its maintainer for the past 10 years,
> > so to remove the 8390 network drivers for good.
> >
> > additionally, 8390 is a kind of old ethernet chip based on
> > ISA interface which is hard to find in the market.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2021-08-09 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 14:56 [PATCH 0/2] net: ethernet: Remove the 8390 network drivers Cai Huoqing
2021-08-07 22:50 ` Michael Schmitz
2021-08-08 19:49 ` Arnd Bergmann
2021-08-08 20:38 ` Michael Schmitz
2021-08-08 21:09 ` Arnd Bergmann
2021-08-09 11:57 ` Geert Uytterhoeven [this message]
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='CAMuHMdXzZfX_mZe==-J52kaUCuM0t-zvFw5aqJTgy8TKJ9Xmvw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=caihuoqing@baidu.com \
--cc=davem@davemloft.net \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=schmitzmic@gmail.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;
as well as URLs for NNTP newsgroup(s).