public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-wireless@vger.kernel.org, David Lin <yu-hao.lin@nxp.com>,
	Brian Norris <briannorris@chromium.org>,
	Francesco Dolcini <francesco@dolcini.it>,
	Johannes Berg <johannes@sipsolutions.net>,
	kernel@pengutronix.de, Jeff Chen <jeff.chen_1@nxp.com>,
	tsung-hsien.hsieh@nxp.com, Stefan Roese <sr@denx.de>
Subject: Re: Future of mwifiex driver
Date: Thu, 6 Mar 2025 11:17:15 +0100	[thread overview]
Message-ID: <20250306101715.GA19853@francesco-nb> (raw)
In-Reply-To: <Z8WM9jn1QFscWZBQ@pengutronix.de>

+ Jeff Chen <jeff.chen_1@nxp.com>, tsung-hsien.hsieh@nxp.com
+ Stefan Roese <sr@denx.de>

Hello Sascha,

On Mon, Mar 03, 2025 at 12:05:26PM +0100, Sascha Hauer wrote:
> I am worried about the future of the mwifiex driver. NXP has an ongoing
> effort of forking the driver to support their new chips, but the forked
> driver lacks support for the old chips supported by the current mwifiex
> driver.
> 
> Overall this leaves us and our customers using the mwifiex driver in a
> very bad situation.  Johannes made clear that he is not going to merge a
> driver that is 70% identical to the existing driver and on the other
> hand the existing driver doesn't get forward due to its odd-fixes state
> and the potential rise of a new driver which would render work on the
> existing driver useless.

While I agree on the challenging situation, I would not call it "very
bad" ... as you know there are multiple people with stake on this driver
(I added SR in Cc here, that I just discovered has some interested on
this).

In the short term I think that improving mwifiex driver is going to be
beneficial for everybody, currently this is not going as smooth as we'd
like, as you wrote and as already commented by Brian.

And the next step would be to figure out how to enable newer Wi-Fi chip
solution from NXP in mainline, we all have our ideas and we are not
moving forward. NXP keeps pushing for a solution that was already
rejected multiple times and so far it was not successful on explaining
why this is the correct way forward. Here I would agree that the
situation is "very bad" at the moment.


> I think part of the solution should be that we start cleaning up the
> mwifiex driver

Ack. I would suggest that we focus on this. I can help with some
review/test (as partially done in the past), but I cannot commit to
actively work on much more than that as of now.

Francesco


  parent reply	other threads:[~2025-03-06 10:17 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
2025-03-06 10:17 ` Francesco Dolcini [this message]
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=20250306101715.GA19853@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=briannorris@chromium.org \
    --cc=jeff.chen_1@nxp.com \
    --cc=johannes@sipsolutions.net \
    --cc=kernel@pengutronix.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sr@denx.de \
    --cc=tsung-hsien.hsieh@nxp.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox