linux-kernel - Re: [PATCH 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family

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: <dd8f294b-425c-4e4a-8eaf-026138461941@ti.com>
Date: Fri, 24 May 2024 10:48:47 +0300
From: "Nemanov, Michael" <michael.nemanov@...com>
To: Kalle Valo <kvalo@...nel.org>
CC: Johannes Berg <johannes.berg@...el.com>, Breno Leitao <leitao@...ian.org>,
        Justin Stitt <justinstitt@...gle.com>,
        Kees Cook <keescook@...omium.org>, <linux-wireless@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, Sabeeh Khan
	<sabeeh-khan@...com>
Subject: Re: [PATCH 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless
 device family

On 5/23/2024 10:15 AM, Kalle Valo wrote:
> The community (myself included) has been frustrated that TI has dropped
> the ball on their existing wireless drivers:
>
> https://docs.kernel.org/process/maintainers.html#ti-wilink-wireless-drivers
>
> This kind of behaviour is not exactly building trust. So how is this
> driver going to be any different?

I understand the frustration. As the engineer leading the development of 
the CC33xx driver I can say that CC3300 and CC3301 are the first in a 
family whose roadmap goes beyond 2030. I can also say that Linux driver 
support is foundational for this line of products and TI is committed to 
supporting these devices in the linux-wireless community for at least 10 
years. Unlike previous drivers, development and maintenance of CC33xx 
will be done by TI engineers and not a 3rd party. Is this acceptable?

Michael.