Unable to receive beacon in IBSS mode

Unable to receive beacon in IBSS mode

[Yeoh Chun-Yeow]

Hi, all

I have observed if you create the interface in the ath10k as IBSS mode
(WMI_VDEV_TYPE_IBSS). The ath10k_wmi_event_mgmt_rx is not able to
receive the beacon frame. This maybe the reason when the STA up as
adhoc mode not able to join the network.

But if you put the ath10k as AP mode (WMI_VDEV_TYPE_AP), you are able
to receive the beacon.

Is this the correct behavior?

Please advice. Thanks

Regards,
Chun-Yeow

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: Unable to receive beacon in IBSS mode

[Kalle Valo]

Yeoh Chun-Yeow <yeohchunyeow@gmail.com> writes:

> I have observed if you create the interface in the ath10k as IBSS mode
> (WMI_VDEV_TYPE_IBSS). The ath10k_wmi_event_mgmt_rx is not able to
> receive the beacon frame. This maybe the reason when the STA up as
> adhoc mode not able to join the network.
>
> But if you put the ath10k as AP mode (WMI_VDEV_TYPE_AP), you are able
> to receive the beacon.
>
> Is this the correct behavior?

I haven't done any IBSS tests myself, but what firmware version are you
using?

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: Unable to receive beacon in IBSS mode

[Yeoh Chun-Yeow]

ath10k: qca988x hw2.0 (0x4100016c) fw 999.999.0.636 api 2 htt 2.1

The firmware version is 999.999.0.636.

----
Chun-Yeow

On Fri, Dec 20, 2013 at 6:17 PM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Yeoh Chun-Yeow <yeohchunyeow@gmail.com> writes:
>
>> I have observed if you create the interface in the ath10k as IBSS mode
>> (WMI_VDEV_TYPE_IBSS). The ath10k_wmi_event_mgmt_rx is not able to
>> receive the beacon frame. This maybe the reason when the STA up as
>> adhoc mode not able to join the network.
>>
>> But if you put the ath10k as AP mode (WMI_VDEV_TYPE_AP), you are able
>> to receive the beacon.
>>
>> Is this the correct behavior?
>
> I haven't done any IBSS tests myself, but what firmware version are you
> using?
>
> --
> Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: Unable to receive beacon in IBSS mode

[Kalle Valo]

Yeoh Chun-Yeow <yeohchunyeow@gmail.com> writes:

> ath10k: qca988x hw2.0 (0x4100016c) fw 999.999.0.636 api 2 htt 2.1
>
> The firmware version is 999.999.0.636.

Ok, that's the firmware version I would recommend to start with. You
could try 10.1 version, but I doubt it works any better with IBSS.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: Unable to receive beacon in IBSS mode

[Yeoh Chun-Yeow]

Hi, Kalle Valo

It seems that the problem of adhoc mode is due to the get_tsf is not
implemented in the driver.

Can you point out which WMI command that we can use to fetch the TSF timestamp.

Thanks

----
Chun-Yeow

On Fri, Dec 20, 2013 at 6:33 PM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Yeoh Chun-Yeow <yeohchunyeow@gmail.com> writes:
>
>> ath10k: qca988x hw2.0 (0x4100016c) fw 999.999.0.636 api 2 htt 2.1
>>
>> The firmware version is 999.999.0.636.
>
> Ok, that's the firmware version I would recommend to start with. You
> could try 10.1 version, but I doubt it works any better with IBSS.
>
> --
> Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: Unable to receive beacon in IBSS mode

[Kalle Valo]

Hi,

Yeoh Chun-Yeow <yeohchunyeow@gmail.com> writes:

> It seems that the problem of adhoc mode is due to the get_tsf is not
> implemented in the driver.
>
> Can you point out which WMI command that we can use to fetch the TSF timestamp.

I took a quick look at firmware and I didn't find a way to do that. But
I'm no firmware engineer so I might have just missed it.

Can you describe in more detail how adhoc is failing?

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: Unable to receive beacon in IBSS mode

[Yeoh Chun-Yeow]

When bringing up the adhoc interface, all of them will do the
beaconing. mac80211 triggers the call to the driver for getting the
latest TSF and tryto merge or join the IBSS with same SSID.

Here in net/mac80211/ibss.c

                 /*
                  * second best option: get current TSF
                  * (will return -1 if not supported)
                  */
                 rx_timestamp = drv_get_tsf(local, sdata);

In example, ath9k_htc has ath9k_htc_get_tsf, but not ath10k. So I am
wondering whether we have get tsf support in firmware.

---
Chun-Yeow

> On Jan 28, 2014 6:29 PM, "Kalle Valo" <kvalo@qca.qualcomm.com> wrote:
>>
>> Hi,
>>
>> Yeoh Chun-Yeow <yeohchunyeow@gmail.com> writes:
>>
>> > It seems that the problem of adhoc mode is due to the get_tsf is not
>> > implemented in the driver.
>> >
>> > Can you point out which WMI command that we can use to fetch the TSF
>> > timestamp.
>>
>> I took a quick look at firmware and I didn't find a way to do that. But
>> I'm no firmware engineer so I might have just missed it.
>>
>> Can you describe in more detail how adhoc is failing?
>>
>> --
>> Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k