linux-kernel - RE: [EXT] Re: [PATCH v3 00/22] wifi: nxpwifi: create nxpwifi to support iw61x

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] [day] [month] [year] [list]

Message-ID:
 <PA4PR04MB96380EE5216693C9CCE16030D1702@PA4PR04MB9638.eurprd04.prod.outlook.com>
Date: Wed, 2 Oct 2024 01:29:10 +0000
From: David Lin <yu-hao.lin@....com>
To: Reto Schneider <rs@....ch>, "linux-wireless@...r.kernel.org"
	<linux-wireless@...r.kernel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"briannorris@...omium.org" <briannorris@...omium.org>, "kvalo@...nel.org"
	<kvalo@...nel.org>, "francesco@...cini.it" <francesco@...cini.it>, Pete Hsieh
	<tsung-hsien.hsieh@....com>, "s.hauer@...gutronix.de"
	<s.hauer@...gutronix.de>
Subject: RE: [EXT] Re: [PATCH v3 00/22] wifi: nxpwifi: create nxpwifi to
 support iw61x

Hi Reto,

> From: Reto Schneider <rs@....ch>
> Sent: Monday, September 30, 2024 4:42 PM
> To: David Lin <yu-hao.lin@....com>; linux-wireless@...r.kernel.org
> Cc: linux-kernel@...r.kernel.org; briannorris@...omium.org;
> kvalo@...nel.org; francesco@...cini.it; Pete Hsieh
> <tsung-hsien.hsieh@....com>; s.hauer@...gutronix.de
> Subject: [EXT] Re: [PATCH v3 00/22] wifi: nxpwifi: create nxpwifi to support
> iw61x
> 
> Hi David,
> 
> Answering here because an OEM proposed using the IW612 in an upcoming
> product of my employer.
> 
> On 30.09.24 08:36, David Lin wrote:
> > [1] We had considered adding IW61x to mwifiex, however due to FW
> >      architecture, host command interface and supported features are
> >      significantly different, doing this on mwifiex will carry a lot of
> >      burdens. The effort of making sure no regression is also a huge
> effort.
> >      We must create a new driver nxpwifi. Subsequent NXP chipsets will
> be
> >      added and sustained on nxpwifi only.
> 
> As developer, this sounds like a huge red flag. In the long-term interest of my
> employer, I'd oppose using this type of hardware in our products even if you
> manage to upstream the driver (as is).
> 
> Kind regards,
> Reto

Mwifiex has been put in “Odds Fixes” state for quite some time. 
Now we have planned to add series of new chips and features. 
Although some of the codes are from Mwifiex, we do spend much effort to enhance the FW/driver interfaces and a few other areas
Our proposal is, mwifiex continues support only existing devices. New NXP connectivity chips and features will be added to nxpwifi only.
We are also committed to regular QA and maintenance for nxpwifi.  

May I know what is your concern on upstream this driver so we can better address it?

David