All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>,
	Pushpal Sidhu <psidhu@gateworks.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: IBSS mode is now supported by CT firmware.
Date: Fri, 28 Nov 2014 08:28:34 -0800	[thread overview]
Message-ID: <5478A2B2.3090402@candelatech.com> (raw)
In-Reply-To: <CAEFj987HmrPz1vsjmckURuC4ZYT2h6MgBT6K3yQTWy3U5s+ZtQ@mail.gmail.com>

I'll investigate the rate-control logic.  I don't know enough
about IBSS currently to know why it would use different rate-ctrl logic than
the normal sta/ap, but hopefully I can figure it out.

Can you post some details on how you configure HT20 v/s legacy mode
for IBSS interfaces?

Do you have any reason to believe the problem is in the driver or mac80211
stack, or is this all a firmware issue?

And, if anyone has a different /AC NIC that can do IBSS, I'm curious
if ath10k will receive at higher speeds?

Thanks,
Ben


On 11/28/2014 03:42 AM, Yeoh Chun-Yeow wrote:
> For CT firmware, IBSS mode works, but again the Rate Control in HT20
> mode is not working at all. It always stuck with 6Mbps Tx Rate.
>
> [  196.030000] ath10k_pci 0000:00:00.0: rx skb 869a5840 len 116 peer
> 04:f0:21:0c:a5:44  ucast sn 95  rate_idx 0 vht_nss 0 freq 5180 band 1
> flag 0x200000 fcs-err 0 mic-err 0 amsdu-more 0
>
> For legacy mode, rate control works. rate_idx to 7 or 54Mbps.
>
> [  156.070000] ath10k_pci 0000:00:00.0: rx skb 86af0900 len 116 peer
> 04:f0:21:0c:a5:1c  ucast sn 95  rate_idx 7 vht_nss 0 freq 5180 band 1
> flag 0x200000 fcs-err 0 mic-err 0 amsdu-more 0
>
> Similar to 636 firmware.
>
> ----
> ChunYeow
>
> On Thu, Nov 27, 2014 at 9:04 AM, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
>> On Thu, Nov 27, 2014 at 6:36 AM, Pushpal Sidhu <psidhu@gateworks.com> wrote:
>>> On Tue, Nov 25, 2014 at 4:59 PM, Ben Greear <greearb@candelatech.com> wrote:
>>>> I still cannot get WPA2 encryption to work, but open authentication
>>>> seems to work fine.  I still have a good bit more testing to do.
>>>> I cannot get ath9k to do encryption in IBSS mode either, so I
>>>> probably am mis-configuring something.
>>>
>>> I don't believe WPA2 is supported with adhoc (at least through
>>> wpa_supplicant). However, WPA should be and while testing your
>>> firmware, I found that it doesn't seem to work (They don't see each
>>> other and thus don't associate).
>>>
>>> I also found that, like the 999.x firmware, the rate's do not go
>>> higher than 54mbit/s. Is this due to the firmware not advertising
>>> proper rates or..?
>>
>> Are you joining the adhoc network in non-HT mode? Anyway, even if you
>> use HT mode, the rate control is not working for 999.x firmware and
>> always stuck at 6Mbps as far as I know.
>>
>> -----
>> Chun-Yeow
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

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

  reply	other threads:[~2014-11-28 16:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26  0:59 IBSS mode is now supported by CT firmware Ben Greear
2014-11-26  1:21 ` Yeoh Chun-Yeow
2014-11-26  1:39   ` Ben Greear
2014-11-26  1:48     ` Yeoh Chun-Yeow
2014-11-26  1:50       ` Ben Greear
2014-11-26  2:14         ` Yeoh Chun-Yeow
2014-11-26  1:57 ` Dave Taht
2014-11-26 22:36 ` Pushpal Sidhu
2014-11-27  1:04   ` Yeoh Chun-Yeow
2014-11-28 11:42     ` Yeoh Chun-Yeow
2014-11-28 16:28       ` Ben Greear [this message]
2014-11-29  0:25         ` Yeoh Chun-Yeow
2014-12-01 17:38         ` Pushpal Sidhu
2014-12-01 17:57           ` Ben Greear
2014-12-04 15:28             ` Sven Eckelmann
2014-12-01 17:13     ` Pushpal Sidhu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5478A2B2.3090402@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=psidhu@gateworks.com \
    --cc=yeohchunyeow@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.