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: <e93e1dd6-c215-4168-83e9-b8199599bc09@hqv.ch>
Date: Mon, 30 Sep 2024 10:41:58 +0200
From: Reto Schneider <rs@....ch>
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, tsung-hsien.hsieh@....com, s.hauer@...gutronix.de
Subject: 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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ