On Wed, Aug 27, 2014 at 2:55 AM, Michal Kazior wrote:
> Avery wrote:
>> Any guesses about why the offchannel time would be too short on ath10k?
>
> Try setting up a larger beacon interval, e.g. 300ms.
wireshark confirmed that the beacon interval was changed, but
offchannel time was weirdly still
On 27 August 2014 08:46, Avery Pennarun wrote:
> On Tue, Aug 19, 2014 at 3:01 AM, Michal Kazior
> wrote:
>> On 19 August 2014 08:30, Kalle Valo wrote:
>>> Yes, my understanding as well is that the ath10k firmware is like that.
>>> But I'm no firmware expert :)
>>>
>>> I assume that the 10.x fir
On Tue, Aug 19, 2014 at 3:01 AM, Michal Kazior wrote:
> On 19 August 2014 08:30, Kalle Valo wrote:
>> Yes, my understanding as well is that the ath10k firmware is like that.
>> But I'm no firmware expert :)
>>
>> I assume that the 10.x firmware does support hw_scan when in AP mode and
>> we would
On Tue, Aug 19, 2014 at 5:56 PM, Adrian Chadd wrote:
> Yeah, but you have to be careful to not drop any queued frames or
> associated station state. Hence why it's done as a separate vdev,
> rather than being done under software channel change control.
That makes sense. So how doomed am I if I w
Yeah, but you have to be careful to not drop any queued frames or
associated station state. Hence why it's done as a separate vdev,
rather than being done under software channel change control.
-a
___
ath10k mailing list
ath10k@lists.infradead.org
http
On Tue, Aug 19, 2014 at 11:23 AM, Adrian Chadd wrote:
> Yes. The whole point is that the firmware knows about the vdev and you
> set the channel on that. The intention is that there's multiple vdevs
> and if they're on different channels (eg STA + P2P, or STA + STA) then
> the firmware can handle
Hi,
Yes. The whole point is that the firmware knows about the vdev and you
set the channel on that. The intention is that there's multiple vdevs
and if they're on different channels (eg STA + P2P, or STA + STA) then
the firmware can handle channel changing, sending sleep notifications
to the AP, b
On 19 August 2014 08:30, Kalle Valo wrote:
> Michal Kazior writes:
>
>> On 19 August 2014 08:07, Kalle Valo wrote:
>>> Avery Pennarun writes:
>>>
>> Are there any plans to implement this feature? It's important in
>> order to implement automatic channel change in case of changes in the
Michal Kazior writes:
> On 19 August 2014 08:07, Kalle Valo wrote:
>> Avery Pennarun writes:
>>
> Are there any plans to implement this feature? It's important in
> order to implement automatic channel change in case of changes in the
> interference environment.
No plans
On 19 August 2014 08:07, Kalle Valo wrote:
> Avery Pennarun writes:
>
Are there any plans to implement this feature? It's important in
order to implement automatic channel change in case of changes in the
interference environment.
>>>
>>> No plans at the moment. Does anyone know h
On 19 August 2014 04:26, Avery Pennarun wrote:
> Hi,
>
> In the ath9k and several other drivers, commands like the following
> work while in AP mode:
>
> iw wlan0 scan -u ap-force passive
> and
Hmm.. I recall seeing a hack for that in OpenWRT codebase. I'd have to
double check that.
> iw wl
Avery Pennarun writes:
>>> Are there any plans to implement this feature? It's important in
>>> order to implement automatic channel change in case of changes in the
>>> interference environment.
>>
>> No plans at the moment. Does anyone know how much work would it be to
>> change mac80211 to su
On Tue, Aug 19, 2014 at 1:50 AM, Kalle Valo wrote:
> Avery Pennarun writes:
>> In the ath9k and several other drivers, commands like the following
>> work while in AP mode:
>>
>> iw wlan0 scan -u ap-force passive
>> and
>> iw wlan0 offchannel 2452 100
>>
>> On ath10k (using a driver from v3.
Avery Pennarun writes:
> In the ath9k and several other drivers, commands like the following
> work while in AP mode:
>
> iw wlan0 scan -u ap-force passive
> and
> iw wlan0 offchannel 2452 100
>
> On ath10k (using a driver from v3.15-rc1 as of April 13th), these tell
> me the operation is no
Hi,
In the ath9k and several other drivers, commands like the following
work while in AP mode:
iw wlan0 scan -u ap-force passive
and
iw wlan0 offchannel 2452 100
On ath10k (using a driver from v3.15-rc1 as of April 13th), these tell
me the operation is not supported.
Are there any plans to
15 matches
Mail list logo