Le Thu, 31 Dec 2009 14:38:35 +0000, Hin-Tak Leung <hintak.leung@xxxxxxxxx> a écrit : > "nobody cares" is not entirely true - AFAIK, code in the staging area > is unreliable/unsuitable/"poor" code which serves the sole purpose of > being there for scavenging and references for re-write (because there > is no equivalent functionality, even alleged, in mainline); so people > looking at the staging code for ideas or references is welcomed. It is > just that there is no hints of any support or vague guarantee that any > of it works for any fitness of purpose. i.e. patches which fix > problems, or migrate functionality out of the staging area to > main-line, are welcomed, but questions and request for help on > understanding or making any of it work, are not. I just bought an wireless usb key based on realtek 8192. If nobody is working on making a driver for it, I'd like to try. But I am wondering where/how to start. Should I follow the TODO file from Greg in staging : ( which seems to merge : rtl8192e rtl8192su rtl8192u ) TODO: - prepare private ieee80211 stack for merge with rtl8187se's version: - remove rtl8192su's specific dead code - cleanup ieee80211.h - move rtl8192su's specific code out from ieee80211.h - abstract rtl819su's specific code - use list_for_each_safe() in ieee80211_crypto_deinit - switch to use shared "librtl" instead of private ieee80211 stack - switch to use LIB80211 - switch to use MAC80211 - switch to use EEPROM_93CX6 - use kernel coding style - checkpatch.pl fixes - sparse fixes - integrate with drivers/net/wireless/rtl818x Or use rtl818x tree to start a new device ? -- Frédéric Leroy -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
