Hi Kalle,

-----Original Message-----
From: Kalle Valo [mailto:kvalo@codeaurora.org]
Sent: Tuesday, August 04, 2015 10:02 AM

Maxime Bizon [off-list ref] writes:

quoted

On Fri, 2015-07-03 at 06:10 +0000, David Lin wrote:

Hello,

quoted

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?

mwl8k was a driver for chips few generations older sponsored by Marvell. We did leverage part of driver framework that is still applicable. However, for the current development, the firmware API specs, chip capabilities and bandwidth requirements have changed in order to handle newer technologies and features.

quoted

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

quoted

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.

No, we are not treating the submission as dumping! We would not have responded with effort to meet the requests/feedback if so. We appreciate and have taken the feedbacks seriously to complete to patch6. In fact the submission was requested by some community members who has seen the benefit of its evolvement on openwrt github, and they would like to see the new driver consolidated into the wireless mainline.

Due to hardware, firmware, specs and requirements change over time, it is not feasible for us to revisit generations old products or making sure new changes are backward compatible with it. (If desired, we welcome the community to take any new useful changes that are independent of chip rev to other similar branches.)

Lastly, I do not think we are creating a precedence with different generation of drivers supporting different families of chips. 
 

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

Sorry, we have missed that email earlier... I hope the above response will suffice to get accepted. Best regards,



 

--
Kalle Valo