Hi Kalle, > -----Original Message----- > From: Kalle Valo [mailto:kvalo@xxxxxxxxxxxxxx] > Sent: Monday, September 07, 2015 4:20 AM > > > Chor Teck Law <ctlaw@xxxxxxxxxxx> writes: > > >> On Tuesday 04 Aug 2015 à 20:02:23 (+0300), Kalle Valo wrote: > >> > >> > I haven't looked at the driver myself yet. Do you have any > >> > estimates how much duplication there is? > >> > > > > I do think that someone interested in this thread should compare the > > two drivers to decide if they want to accept mwlwifi (or we let it > > develop closed door). > > > > You will find the differences with some leverage. To make your > > comparison easier, here is the summary (excluding the patch1-patch6 > > improvements as per review feedbacks from Johannes and community): > > > > mwlwifi functions leveraged from mwl8k: > > - 802.11n setting for mac80211 > > - Functions needed to hook up to mac80211 > > - Interactions with mac80211 to establish BA streams > > - Partial firmware APIs, some data fields > > - Method to pass rx packets to mac80211 (but added with 11ac rate > > map/reports) > > > > All others are different/new. Including some listed below: > > - Different/new 11ac chipsets, including combo BT devices > > - Added support for 11ac related settings and functions > > - Added support for concurrent AP+STA functionalities with single > > firmware per chip > > - Additional firmware APIs > > - Added functions to convert newly supported settings from mac80211 > to > > firmware > > - Different Tx datapath > > - Different Rx low level datapath (though data structure for > receiving > > is same) > > - Reorganized the files for future scalability and features addition > > (more to come) > > - Addressed all (sort of) review feedbacks from patch1-patch6 of this > > submission > > 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. 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. Thanks Chor-Teck ��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
