From: Kalle Valo <kvalo@codeaurora.org>
To: Chor Teck Law <ctlaw@marvell.com>
Cc: David Lin <dlin@marvell.com>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>, Pete Hsieh <peteh@marvell.com>
Subject: Re: [PATCH v5] Add new mac80211 driver mwlwifi.
Date: Tue, 29 Sep 2015 12:03:14 +0300 [thread overview]
Message-ID: <87eghh7g30.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5743c7447a834df1bf719dfa3444e9cd@SC-EXCH03.marvell.com> (Chor Teck Law's message of "Fri, 11 Sep 2015 13:43:37 +0000")
Chor Teck Law <ctlaw@marvell.com> writes:
>> You have named the new driver as mwlwifi, which is a really generic
>> name. Does that imply that mwlwifi will start supporting more Marvell
>> devices in the future?
>
> Yes, that is the plan on same generation of 11ac chipset that support
> host-based mac80211.
>
>> Or will be in the situation that you fork the
>> driver again and we end up having mwlwifi2, mwlwifi3 and so on?
>>
>
> We do intend to add interface HAL spec version to mwlwifi in case the
> lower HAL becomes unavoidably changed in future, so that we can
> continue to maintain mwlwifi.
Very good.
> But for different generation of future chipsets/new technology, when
> the hardware no longer permit us to use same driver, we will have to
> re-evaluate our options. We cannot guarantee something way out into
> the future.
Yeah, that's understandable. But the community really dislikes having
duplicated code/functionality, so please keep this in mind.
If you can submit the next version soon we could try to get this driver
to 4.4. We have few more weeks.
--
Kalle Valo
next prev parent reply other threads:[~2015-09-29 9:03 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
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 [this message]
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=87eghh7g30.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=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 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.