On Mon, May 19, 2008 at 02:16:08PM +0200, Johannes Berg wrote: > > > Instead of testing for wireless/, best thing would probably be to call > > SIOCGIWRANGE on the device and if it returns EOPNOTSUP then it's not > > wireless. Some drivers may have to load firmware to figure out > > supported rates and encryption capabilities, but to be honest, NM does > > this to detect wireless devices and I haven't run into any issues in 4 > > years using it. If there are issues with drivers, then we need to fix > > the driver too. > > I was about to propose calling SIOCGIWNAME since that is what > wireless-tools do and that linux/wireless.h indicates. > > johannes Yes, using SIOCGIWNAME is the right way to do it, it's the only ioctl that is guarantee to always be present and require minimal processing from the driver (it should be a static string). If you look at iwconfig, this is how it does it. (Sorry for the delay replying, I was chasing kids and electrical faults this week end). Have fun... Jean -- 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
