On Mon, Jul 26, 2010 at 3:00 PM, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: > On 07/26/2010 12:49 PM, Ben Greear wrote: >> >> This is with today's wireless-testing (with no extra hacks) > > Maybe a better question: In 2.6.31 you could mount debugfs at /debug > and get the state with: > cat /debug/ieee80211/sta0/state debugfs is not static API. In fact that's a big reason why we use it. I considered defining a filesystem API for 802.11 using configfs but our priority is to first get nl80211 feature-complete with respect to wext, which we have completed now. But anyway, debugfs is *not* API and you should not rely on it, if you want to define API consider configfs. > It seems in .34 there is only phy0 info in debugfs. Or, am I > just not looking in the right place? > > I don't mind hacking code, but I'd appreciate a pointer to the > right part of the code if anyone has suggestions. The other thing you pointed out with wext, you should stop using wext and instead rely on nl80211. It is true that if you see something on /proc/net/wireless/ that was there before but not there now it is a regression and it should be addressed. Not sure where the status crap comes from on wext. Luis -- 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
