Hi James, How did you know that by downgrading the firmware the problem has been solved?. Did you see a scenario or flow in the driver that both occurred when using the two different firmware but able to work on the p80?. The reason why I am asking is because sometimes the bug/s did not occur often. Regards, john On Thu, Apr 24, 2014 at 12:28 AM, Bing Zhao <bzhao@xxxxxxxxxxx> wrote: > Hi James, > >> > > > I'm interested to know if the "firmware hangs" that you experiment >> > > > with prevent autonomous RF TX, or if RF TX typically proceeds. >> > > >> > > It depends. Even if firmware hangs the hardware is still alive. >> > > So you could see beacons and probe responses from the card if >> > > hardware has been programmed before firmware hangs. >> > >> > Thanks. I neglected to mention the time period; beacons and probe >> > responses are seen for many minutes after the timeout report by the >> > driver, and I have not yet tested for how long this lasts. The probe >> > responses are in reply to new probe requests. It makes me think the >> > card is working fine, apart from not communicating with the host. >> >> Downgrading wireless firmware to 14.66.9.p80 has fixed this problem. > > Wow! It means that p96 firmware had introduced the problem. > > Thanks, > Bing > -- 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
