On Sat, Feb 21, 2009 at 2:57 AM, Kalle Valo <kalle.valo@xxxxxx> wrote: > Jason Andryuk <jandryuk@xxxxxxxxx> writes: > >> I thought before I was not getting any scan results. I may have been >> wrong. However right now with the driver from wireless-testing >> 2009-02-18, 4 APs show up in NetworkManager. Unfortunately, my AP is >> not one of them. > > What's your distance to the AP? Maybe twenty feet through some walls. I successfully tested with a Windows machine and the adapter in more or less the same place. >> No signal strength is reported for any of them. > > Yes, this is a know issue. I'll try to fix it soon. > >> Curiously, there are distinct results for each of at76c50x-usb, a >> semi-operational iwl3945 and the functional rtl8187. >> >> CMD_SCAN is receiving a lot of status 0x03 CMD_STATUS_INVALID_PARAMETER >> >> With debug=0xf022c001 I get the output below. I was wondering if >> status=0x03 was being received because CMD_SET_MIB was called before >> CMD_SCAN's status was checked. Hopefully you can make some sense out >> of the below logs. > > After a quick look I didn't find anything, but I will investigate this > more. > > Is at76_usb (the staging driver) is working fine with your device? Can > you take logs from it so that we can compare? How do scan results get returned from the device to the host computer? I can't see any place that the scans are actually received. Does the rx_tasklet handle this? Are the few listed scan results just those that are extracted by mac80211? I ask because you can see the calls to ieee80211_rx_irqsafe. I was trying at76_usb + mac80211 when that was in staging, but I have not tried ~ at76c503a.berlios.de staging version. I can take a look. Jason -- 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
