All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-wireless@vger.kernel.org
Cc: 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
Subject: Future of mwifiex driver
Date: Mon, 3 Mar 2025 12:05:26 +0100	[thread overview]
Message-ID: <Z8WM9jn1QFscWZBQ@pengutronix.de> (raw)

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.

I think part of the solution should be that we start cleaning up the
mwifiex driver so that at one point it could

a) be a robust base for a fork, or
b) make the fork unnecessary

This would help people using the mwifiex driver to get a better support
for their hardware.  It would also help NXP by splitting the necessary
changes into easier swallowable parts that are actually reviewable.
Should we really need a fork at some point then much of the review would
have already been done.

I have a series here [1] doing some cleanup work which I'd still like to
get forward.  Johannes made some remarks in [2] and [3] on which parts
of the driver need cleanup. Some more things for cleanup can also be
found in the forked driver code.

I am willing to put more work into the driver in creating and also
reviewing and testing patches, but I would need some path forward for
the driver and I think this needs a commitment from NXP to take the
detour over the mwifiex driver to get their stuff upstream.

Any thoughts?

[1] https://lore.kernel.org/linux-wireless/87ldwyumvq.fsf@kernel.org/
[2] https://lore.kernel.org/lkml/57ff2078632d8f14ca73c8307dc43585b3d09f50.camel@sipsolutions.net/#r
[2] https://lore.kernel.org/lkml/5f5c42585e168e252a5fa3f43325aaa360f6d27a.camel@sipsolutions.net/

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

             reply	other threads:[~2025-03-03 11:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 11:05 Sascha Hauer [this message]
2025-03-04  1:45 ` Future of mwifiex driver 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
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=Z8WM9jn1QFscWZBQ@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=briannorris@chromium.org \
    --cc=francesco@dolcini.it \
    --cc=johannes@sipsolutions.net \
    --cc=kernel@pengutronix.de \
    --cc=linux-wireless@vger.kernel.org \
    --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.