Hi, >> Well so just >> But according to >> http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2010-October/002175.html >> the compat-rt2x00 tarballs seem to be made manually? > > Too lazy to check that, best thing might be to just focus on upstream > development, ensuring patches get into linux-next.git and having your > users just use the daily tarballs and stable releases for stable > stuff. The compat-rt2x00 package only contains the experimental patches, which are not always ready for upstream usage. It exists for testing purposes. Not all patches inside the experimental tree will be moved upstream, they often cause a lot of crashes and are often incomplete. Basically the package only exists for some people who want to test the latest rt2x00 code the first. The mac80211 code inside the package usually lags a few days behind compat-wireless, simply because I don't always care for the latest mac80211 version. ;) >> Sorry for stupid questions, I want to get into rt2x00 development >> but I need to target a stable 2.6.32 kernel and I'm trying to figure >> out which git tree to base my work on. > > My advice, work on wireless-testing.git, send patches ASAP, and let > them propagate. Use the daily tarballs for user testing and for stable > release you can support users using the stable compat-wireless > releases. For rt2x00 development you can choose between rt2x00.git and wireless-testing.git, the trees are usually not that far apart, since smaller patches are pushed quite quickly upstream. (Also rt2x00.git is rebased frequently, while wireless-testing.git rarely is rebased) Ivo -- 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
