From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>,
Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: CT and AP firmware not allowed beaconing in adhoc mode
Date: Wed, 25 Jun 2014 05:39:51 -0700 [thread overview]
Message-ID: <53AAC317.4050403@candelatech.com> (raw)
In-Reply-To: <CA+BoTQnnrjhUK_ZPwpG-L+wQ=suisNrkb1Tdhdww4ueMpAvDwQ@mail.gmail.com>
On 06/25/2014 05:33 AM, Michal Kazior wrote:
> On 25 June 2014 06:50, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
>> Hi, all
>>
>> Both CT and AP firmware seem not allow beaconing in adhoc mode.
>> Anyone will fix this?
>
> AP firmware doesn't really support IBSS. I guess ath10k shouldn't
> advertise the iftype if 10.1 firmware is used.
>
> As far as I know CT firmware is based on the AP firmware branch which
> means no IBSS as well.
That is true. I have not had any time to see what it would take
to support IBSS in the 10.1.x firmware, and do not have access to the
999.x source to see what it does differently.
I'm not sure when I'll have time to work on it....
Thanks,
Ben
--
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
next prev parent reply other threads:[~2014-06-25 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 4:50 CT and AP firmware not allowed beaconing in adhoc mode Yeoh Chun-Yeow
2014-06-25 12:33 ` Michal Kazior
2014-06-25 12:39 ` Ben Greear [this message]
2014-06-26 7:40 ` Yeoh Chun-Yeow
2014-06-26 7:43 ` Adrian Chadd
2014-06-26 12:56 ` Ben Greear
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=53AAC317.4050403@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=michal.kazior@tieto.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.