On Mon, Nov 16, 2009 at 05:01:09PM -0800, Luis R. Rodriguez wrote: > If a few developers still exist who are committed to helping maintain > madwifi until ath5k gets feature-parred the easiest solution now > (since the HAL is open) is to just throw it into staging and hopefully > that'll attract more developers to help keep it up to date with actual > current kernels. For the record, I would be generally opposed to adding madwifi to drivers/staging. We already have enough trouble with duplication of hardware support between drivers/staging and drivers/net/wireless. If madwifi has features that people need/want and that ath5k/mac80211 still lacks, lets talk about how to get them (or reasonabe replacements for them) into the mainline kernel. I'm sure some ideas will meet some resistance, but if someone is motivated to continue pursuing maintenance of madwifi than they should be motivated enough to at least try to convince the rest of us why those features are worth having in net/wireless, net/mac80211, and/or drivers/net/wireless. Even if the solution is some quirky thing that "normal" people will ignore, it is bound to be better to have mainline support than to continue working out-of-tree. John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- 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
