From: Andrew Lunn <andrew@lunn.ch>
To: Birger Koblitz <mail@birger-koblitz.de>
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/9] ax88179_178a: Add support for ethtool pause parameter configuration
Date: Tue, 7 Jul 2026 17:27:28 +0200 [thread overview]
Message-ID: <33b35184-e962-44ca-b0c1-ba9beb08c341@lunn.ch> (raw)
In-Reply-To: <833f79c1-39be-4c04-bc4f-3ec7a983ab56@birger-koblitz.de>
> For me the way ahead is to stick with the simple MII-driver and just make sure that
> features such as pause configuration are properly implemented. Please tell me if that
> makes sense or there are better ways.
The better way forward is to refuse to support the device in Mainline,
until the vendor produces a firmware version which is not FUBAR.
The PHY ID is a contract, it states compatibility. If different
firmware gives it a different API, it must have a different ID.
Mainline can push back on vendors. We can say only their out of tree
vendor crap driver will be used with their hardware, if they don't
follow the basic rules as defined in 802.3.
There are plenty of USB dongles what just work in Linux, because they
follow the rules. So i don't see it as being a particularly big loss
to Mainline.
Andrew
next prev parent reply other threads:[~2026-07-07 15:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 5:42 [PATCH 0/9] ax88179_178a: Add support for AX88179A-based chips Birger Koblitz
2026-07-01 5:42 ` [PATCH 1/9] ax88179_178a: Fix endianness of pause watermark register Birger Koblitz
2026-07-01 14:57 ` Andrew Lunn
2026-07-01 5:42 ` [PATCH 2/9] ax88179_178a: Add HW support for AX179A-based chips Birger Koblitz
2026-07-01 15:05 ` Andrew Lunn
2026-07-07 9:11 ` Paolo Abeni
2026-07-01 5:42 ` [PATCH 3/9] ax88179_178a: Add support for AX88179A MMD access Birger Koblitz
2026-07-01 9:53 ` Maxime Chevallier
2026-07-01 5:42 ` [PATCH 4/9] ax88179_178a: Obtain speed and duplex from Interrupt URB Birger Koblitz
2026-07-01 5:42 ` [PATCH 5/9] ax88179_178a: Add support for ethtool pause parameter configuration Birger Koblitz
2026-07-01 10:04 ` Maxime Chevallier
2026-07-01 15:08 ` Andrew Lunn
2026-07-01 16:22 ` Birger Koblitz
2026-07-01 17:05 ` Andrew Lunn
2026-07-01 17:45 ` Birger Koblitz
2026-07-01 18:41 ` Andrew Lunn
2026-07-06 6:28 ` Birger Koblitz
2026-07-07 15:27 ` Andrew Lunn [this message]
2026-07-01 5:42 ` [PATCH 6/9] ax88179_178a: Add VLAN offload support for AX88179A Birger Koblitz
2026-07-01 5:42 ` [PATCH 7/9] ax88179_178a: Add ethtool get_drvinfo Birger Koblitz
2026-07-01 5:42 ` [PATCH 8/9] ax88179_178a: Add support for AX88179A/772D/279 EEPROM access Birger Koblitz
2026-07-01 5:42 ` [PATCH 9/9] ax88179_178a: Add AX179A/AX279 multicast configuration Birger Koblitz
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=33b35184-e962-44ca-b0c1-ba9beb08c341@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mail@birger-koblitz.de \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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