linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: mbizon@freebox.fr
Cc: David Lin <dlin@marvell.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>,
	Chor Teck Law <ctlaw@marvell.com>, Pete Hsieh <peteh@marvell.com>
Subject: Re: [PATCH v5] Add new mac80211 driver mwlwifi.
Date: Tue, 04 Aug 2015 20:02:23 +0300	[thread overview]
Message-ID: <87vbcvyokg.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1436455659.36587.131.camel@sakura.staff.proxad.net> (Maxime Bizon's message of "Thu, 09 Jul 2015 17:27:39 +0200")

Maxime Bizon <mbizon@freebox.fr> writes:

> On Fri, 2015-07-03 at 06:10 +0000, David Lin wrote:
>
> Hello,
>
>> The Linux driver for WRT1900AC. The work was initially developed as
>> part of openwrt effort and maintained on
>> https://github.com/kaloz/mwlwifi.
>
> I see *massive* code duplication with the mwl8k driver.

I haven't looked at the driver myself yet. Do you have any estimates how
much duplication there is?

> This is, I guess, not a surprise since the supported chipset are an
> evolution of the ones supported by mwl8k, just look at how close/similar
> the descriptor format is.
>
> The problem is that each new Marvell chipset comes with a new firmware
> version, and there is no effort to have a common firmware API or code
> base that supports multiple chipsets.
>
> That pushes the bloat on the kernel side, do we really agree on that ?

That is a very good question. The kernel should not be a dumping ground
for random drivers which duplicate lots of code but this is a sort of
gray area and depends on the case.

Did Marvell reply to this? I didn't find any comments about this.

-- 
Kalle Valo

  reply	other threads:[~2015-08-04 17:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  6:10 [PATCH v5] Add new mac80211 driver mwlwifi David Lin
2015-07-03  9:51 ` Johannes Berg
2015-07-08  0:14   ` David Lin
2015-07-04 10:40 ` Jonas Gorski
2015-07-05 10:33   ` Johannes Berg
2015-07-05 10:57     ` Jonas Gorski
2015-07-07  1:47   ` David Lin
2015-07-07  9:38     ` Jonas Gorski
2015-07-07  9:50       ` Imre Kaloz
2015-07-07 13:48         ` Chor Teck Law
2015-07-07 14:20           ` Jonas Gorski
2015-07-07 14:35           ` Imre Kaloz
2015-07-07 14:56             ` Chor Teck Law
2015-07-09 15:27 ` Maxime Bizon
2015-08-04 17:02   ` Kalle Valo [this message]
2015-08-04 18:11     ` Chor Teck Law
2015-08-04 22:49       ` Maxime Bizon
2015-09-07 10:37         ` Kalle Valo
2015-08-04 22:09     ` Maxime Bizon
2015-08-05  8:39       ` Chor Teck Law
2015-08-05 14:21         ` Maxime Bizon
2015-08-05 15:29           ` Chor Teck Law
2015-09-07 11:20         ` Kalle Valo
2015-09-11 13:43           ` Chor Teck Law
2015-09-29  9:03             ` Kalle Valo
2015-09-29 10:11               ` Kalle Valo
2015-09-30  2:05                 ` David Lin

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=87vbcvyokg.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=ctlaw@marvell.com \
    --cc=dlin@marvell.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mbizon@freebox.fr \
    --cc=peteh@marvell.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;
as well as URLs for NNTP newsgroup(s).