On 3-4-2017 23:39, Tobin C. Harding wrote: > On Mon, Apr 03, 2017 at 12:15:15PM +0200, Arend Van Spriel wrote: >> seems we are missing out again? > > Sorry, I don't understand what this comment means? My bad. I had to reset my email account in thunderbird and now it needs to learn anew what is spam and what is not. So I missed out on the conversation as some messages (a lot actually) ended up in my spam folder. >> On 3-4-2017 11:50, Toke Høiland-Jørgensen wrote: >>> "Tobin C. Harding" <me@xxxxxxxx> writes: >>> >>>> Except one: do you know off the top of your head of a canonical >>>> implementation of a softmac wi-fi driver. >>> >>> I'll suggest taking a look at the ath9k driver :) >> >> Looking at ks7010 driver it looks like it has 802.11 stack in firmware >> and not sure if Renesas is actively supporting this effort to come up >> with mac80211-friendly firmware or provide detailed chip info. > > Thanks for taking a look. If the ks7010 driver has 802.11 stack in > firmware does that mean it is not compatible with using the kernel > mac80211 stack with the current firmware? I do not have my hopes up > about getting any chip information out of Renesas, all I think we have > to go in is the current WEXT driver. Indeed. That is my gut feeling as well and if that is truly the case your best option would be a cfg80211-based driver like ath6kl, mwifiex, and brcmfmac. > This is an exercise in learning for me, but I do not want to take any > ones time up with a project that is not that useful. Is getting the > ks7010 driver out of staging something that is of use to the kernel > community or are there other wi-fi tasks that our time is better spent > on? If there are linux users with this hardware than sure. Especially if it revised to interface with the latest wireless subsystem so tools like iw can operate on it. Also I suppose it is preferred if a driver is maintained. I do not see the ks7010 listed in the MAINTAINERS file yet. > thanks, > Tobin. > _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
