lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250929090229.2fa33931.michal.pecio@gmail.com>
Date: Mon, 29 Sep 2025 09:02:29 +0200
From: Michal Pecio <michal.pecio@...il.com>
To: yicongsrfy@....com
Cc: oneukum@...e.com, andrew+netdev@...n.ch, davem@...emloft.net,
 edumazet@...gle.com, kuba@...nel.org, marcan@...can.st, pabeni@...hat.com,
 linux-usb@...r.kernel.org, netdev@...r.kernel.org, yicong@...inos.cn
Subject: Re: [PATCH v2 1/3] Revert "net: usb: ax88179_178a: Bind only to
 vendor-specific interface"

On Mon, 29 Sep 2025 13:31:43 +0800, yicongsrfy@....com wrote:
> From: Yi Cong <yicong@...inos.cn>
> 
> This reverts commit c67cc4315a8e605ec875bd3a1210a549e3562ddc.
> 
> Currently, in the Linux kernel, USB NIC with ASIX chips use the cdc_ncm
> driver.

Only those with a CDC configuration. Mine doesn't have any.

> However, this driver lacks functionality and performs worse than
> the vendor's proprietary driver.

Is this reason to revert a commit which prevents the vendor driver
binding to CDC or other unwanted interfaces?

The original commit assumed that the vendor driver will never need
to bind to them. What has changed?

Isn't it a regression?

Regards,
Michal

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ