All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
	linux-wireless@vger.kernel.org, David Lin <yu-hao.lin@nxp.com>,
	Francesco Dolcini <francesco@dolcini.it>,
	kernel@pengutronix.de
Subject: Re: Future of mwifiex driver
Date: Tue, 18 Mar 2025 18:14:23 -0700	[thread overview]
Message-ID: <Z9oabwPsFJEJKaAD@google.com> (raw)
In-Reply-To: <2587f323fe19b33d2e9ec49bdc3979f71b9c0ba0.camel@sipsolutions.net>

On Fri, Mar 07, 2025 at 09:48:13AM +0100, Johannes Berg wrote:
> But copying an old crappy driver for the sake of "we don't want to
> maintain an old crappy driver" is a really bad argument to make?!

Is that the argument? Honest question. It's not really clear to me.

From
https://lore.kernel.org/all/20240930063701.2566520-1-yu-hao.lin@nxp.com/:

> [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.

That sounds like you noted one of their reasons ("making sure no
regression is also a huge effort"), but they also claim the FW
architecture and host command interface is significantly different. I
don't recall seeing a proper discussion of that -- although Sascha seems
to claim [1] it wasn't that hard for him to support iw61x via mwifiex.

Brian

[1] https://lore.kernel.org/all/Z8rGDTjkwKAVaREL@pengutronix.de/

  parent reply	other threads:[~2025-03-19  1:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 11:05 Future of mwifiex driver Sascha Hauer
2025-03-04  1:45 ` Brian Norris
2025-03-07  8:48   ` Johannes Berg
2025-03-07  9:47     ` Sascha Hauer
2025-03-19  1:14     ` Brian Norris [this message]
2025-03-06 10:17 ` Francesco Dolcini
2025-03-07 10:10   ` Sascha Hauer
2025-03-19 10:32     ` Francesco Dolcini
2025-03-26 12:19       ` Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z9oabwPsFJEJKaAD@google.com \
    --to=briannorris@chromium.org \
    --cc=francesco@dolcini.it \
    --cc=johannes@sipsolutions.net \
    --cc=kernel@pengutronix.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=yu-hao.lin@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.