On Thu, 2017-01-05 at 15:38 +0100, Jorge Ramirez wrote:
> do you mean this?
>
> [jramirez@igloo ~ (debian-qcom-dragonboard410c-16.09-local $)]$ git
> diff
> diff --git a/net/wireless/wext-sme.c b/net/wireless/wext-sme.c
> index a4e8af3..c56bac5 100644
> --- a/net/wireless/wext-sme.c
> +++
On 01/05/2017 03:06 PM, Johannes Berg wrote:
I am not sure it matters - if I understood your reply, there is no
valid use case to change the frequency in that mode (and all that
code should be removed);
All of wext *is* being removed - slowly :)
It's not longer default in the kernel
> I am not sure it matters - if I understood your reply, there is no
> valid use case to change the frequency in that mode (and all that
> code should be removed);
All of wext *is* being removed - slowly :)
It's not longer default in the kernel configuration now.
IIRC, there actually was a
On 01/05/2017 12:38 PM, Johannes Berg wrote:
+linux-wireless, where this should've gone
nice. thanks and apologies.
I am running a single wlan0 interface in managed mode (no aliases,
no other wireless interfaces).
The association with the AP still hasn't happened.
I noticed that if
+linux-wireless, where this should've gone
> I am running a single wlan0 interface in managed mode (no aliases,
> no other wireless interfaces).
> The association with the AP still hasn't happened.
>
> I noticed that if trying to change the frequency to one of the valid
> values, the driver
Hello all,
I am running a single wlan0 interface in managed mode (no aliases, no
other wireless interfaces).
The association with the AP still hasn't happened.
I noticed that if trying to change the frequency to one of the valid
values, the driver returns EBUSY.
The call stack is
