Initial Linux-wireless contribution

[Eugene Krasnikov]

> But who maintains wcnss_core?

Good question, I wish i know:(
I just did not want to implement wcnss_core from the very beginning.
So suggestion is to contact wcnss_core maintainers and see how open
they are. If that is difficult, then we just and additional layer
between wcnss_core and wcn36xx. How does that sound?

2013/8/5 Kalle Valo <kvalo at qca.qualcomm.com>:
> Eugene Krasnikov <k.eugene.e at gmail.com> writes:
>
>> My understanding is that wcnss_core IS that glue layer between
>> platform and wcn36xx. So my idea was to move "struct ieee80211_hw
>> *private_hw" somehow to the wcnss_core? Or at least store it there.
>> What do you think about that idea?
>
> Ok, so basically your idea is that instead of wnc36xx-msm.ko we will use
> wcnss_core.ko to implement the platform struct?
>
> But who maintains wcnss_core? Will they accept patches from us? In my
> opinion it would be easier and more reliable that we mantain the glue
> layer ourselves.
>
> --
> Kalle Valo



-- 
Best regards,
Eugene