On 22 June 2015 at 16:01, Krishna Chaitanya chaitanya.m...@gmail.com wrote:
On Mon, Jun 22, 2015 at 6:32 PM, Michal Kazior michal.kaz...@tieto.com
wrote:
On 22 June 2015 at 13:56, Krishna Chaitanya chaitanya.m...@gmail.com wrote:
On Mon, Jun 22, 2015 at 5:13 PM, Janusz Dziedzic
On Mon, Jun 22, 2015 at 5:13 PM, Janusz Dziedzic
janusz.dzied...@tieto.com wrote:
In case we will get ROC abort we should not call
ieee80211_remain_on_channel_expired().
In other case I hit such warning on MIPS and
p2p negotiation failed (tested with use_chanctx=1).
ath: phy0: Starting RoC
In case we will get ROC abort we should not call
ieee80211_remain_on_channel_expired().
In other case I hit such warning on MIPS and
p2p negotiation failed (tested with use_chanctx=1).
ath: phy0: Starting RoC period
ath: phy0: Channel definition created: 2412 MHz
ath: phy0: Assigned next_chan to
On 22 June 2015 at 13:56, Krishna Chaitanya chaitanya.m...@gmail.com wrote:
On Mon, Jun 22, 2015 at 5:13 PM, Janusz Dziedzic
janusz.dzied...@tieto.com wrote:
In case we will get ROC abort we should not call
ieee80211_remain_on_channel_expired().
In other case I hit such warning on MIPS and
On Mon, Jun 22, 2015 at 6:32 PM, Michal Kazior michal.kaz...@tieto.com wrote:
On 22 June 2015 at 13:56, Krishna Chaitanya chaitanya.m...@gmail.com wrote:
On Mon, Jun 22, 2015 at 5:13 PM, Janusz Dziedzic
janusz.dzied...@tieto.com wrote:
In case we will get ROC abort we should not call