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: <20250929072513.3136507-1-yicongsrfy@163.com>
Date: Mon, 29 Sep 2025 15:25:13 +0800
From: yicongsrfy@....com
To: michal.pecio@...il.com,
	oneukum@...e.com,
	andrew+netdev@...n.ch,
	davem@...emloft.net,
	edumazet@...gle.com,
	kuba@...nel.org
Cc: 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 09:02:29 +0200, Michal Pecio <michal.pecio@...il.com> wrote:
>
> On Mon, 29 Sep 2025 13:31:43 +0800, yicongsrfy@....com wrote:
> > From: Yi Cong <yicong@...inos.cn>

> > 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?

This series of patches aims to resolve the compatibility issues of devices
that have both CDC configurations and vendor-specific configurations.

In my understanding, avoiding the use of the vendor driver when it could
be used is merely a workaround; a better approach is to directly address
and solve the underlying problem.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ