On Sun, Feb 8, 2015 at 3:17 PM, Janusz Dziedzic <janusz.dziedzic@xxxxxxxxx> wrote: > On 8 February 2015 at 11:57, Eliad Peller <eliad@xxxxxxxxxx> wrote: >> On Sat, Feb 7, 2015 at 9:17 PM, Janusz Dziedzic >> <janusz.dziedzic@xxxxxxxxx> wrote: >>> BTW, what in case we will start AP on first interface (DFS channel), >>> on second one we will try to connect to other AP. As I understand this >>> correctly, second iface (STA iface) will not allow to scan (connect) >>> ...? >>> >> right. >> The rationale behind it that you must listen constantly to detect >> radar events, which prevents scanning off-channel. >> (i guess an exception for on-channel scanning can be added if needed, though) >> > Still I can image hw with hw_scan() support that could have dedicated > "hw part" for scanning. > So, driver should made this decision (allow or not) base on hw features. > this will probably require additional radio... anyway, i don't have any objection here :) just explained the original logic (and my patch only changed the behavior from blocking indefinitely to returning error immediately) Eliad. -- 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
