Channels (frequencies) are getting more details that users may want to
know about. E.g. it's important to know which frequencies allow using
40/80/160 MHz channels to setup AP properly.
We list channels in "info" command output but it's already quite big and
it was agreed to introduce new command
On Fri, 2016-05-20 at 12:13 +0200, Rafał Miłecki wrote:
> Channels (frequencies) are getting more details that users may want
> to
> know about. E.g. it's important to know which frequencies allow using
> 40/80/160 MHz channels to setup AP properly.
>
> We list channels in "info" command output bu
On 31 May 2016 at 12:16, Johannes Berg wrote:
> On Fri, 2016-05-20 at 12:13 +0200, Rafał Miłecki wrote:
>> Channels (frequencies) are getting more details that users may want
>> to
>> know about. E.g. it's important to know which frequencies allow using
>> 40/80/160 MHz channels to setup AP proper
On Tue, 2016-05-31 at 15:10 +0200, Rafał Miłecki wrote:
> > Unfortunately, I get compiler warnings about width_* being possibly
> > used uninitialized. Can you address that please?
> It's nice your compiled got this mistake, my didn't. There were
> actually meant to be static. I'll fix that.
I ac
On 31 May 2016 at 15:14, Johannes Berg wrote:
> On Tue, 2016-05-31 at 15:10 +0200, Rafał Miłecki wrote:
>
>> > Unfortunately, I get compiler warnings about width_* being possibly
>> > used uninitialized. Can you address that please?
>> It's nice your compiled got this mistake, my didn't. There wer
On 31 May 2016 at 17:58, Rafał Miłecki wrote:
> On 31 May 2016 at 15:14, Johannes Berg wrote:
>> On Tue, 2016-05-31 at 15:10 +0200, Rafał Miłecki wrote:
>>
>>> > Unfortunately, I get compiler warnings about width_* being possibly
>>> > used uninitialized. Can you address that please?
>>> It's nic
