Kalle Valo <kvalo@xxxxxxxxxxxxxx> writes: > Ajay Singh <ajay.kathat@xxxxxxxxxxxxx> writes: > >> Hi Greg, >> >> We all are working on submitting and reviewing patches for wilc1000 in >> staging driver for quite some time. >> >> We would like to have feedback on the next steps to bring wilc1000 >> driver closer to move into the wireless subsystem tree. >> >> In summary, the following major things from TODO have been addressed in >> staging: >> -remove the defined feature as kernel versions >> -remove OS wrapper functions >> -remove custom debug and tracing functions >> -rework comments and function headers(also coding style) >> -remove build warnings >> -replace all semaphores with mutexes or completions >> -make spi and sdio components coexist in one build >> -turn compile-time platform configuration (BEAGLE_BOARD, PANDA_BOARD, >> PLAT_WMS8304, PLAT_RKXXXX, CUSTOMER_PLATFORM, ...) into run-time >> options that are read from DT >> -replace SIOCDEVPRIVATE commands with generic API functions >> -use wext-core handling instead of private SIOCSIWPRIV implementation > > From wireless point of view: if I see wext mentioned anywhere in the > driver I stop right there. cfg80211 is a hard requirement for us > nowadays. Clarification: Depending on the hardware design either cfg80211 or mac80211 is a hard requirement. I haven't checked wilc1000 at all so I don't know what design it has but if it's a "softmac" design then it has to use mac80211, we do not want to support multiple 802.11 UMAC stacks. -- Kalle Valo _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
