CT and AP firmware not allowed beaconing in adhoc mode

CT and AP firmware not allowed beaconing in adhoc mode

[Yeoh Chun-Yeow]

Hi, all

Both CT and AP firmware seem not allow beaconing in adhoc  mode.
Anyone will fix this?

Regards,
ChunYeow

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

Re: CT and AP firmware not allowed beaconing in adhoc mode

[Michal Kazior]

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.


Michał

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

Re: CT and AP firmware not allowed beaconing in adhoc mode

[Ben Greear]

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

Re: CT and AP firmware not allowed beaconing in adhoc mode

[Yeoh Chun-Yeow]

Not possible for all the modes to be supported in one single firmware?

----
Chun-Yeow

On Wed, Jun 25, 2014 at 8:39 PM, Ben Greear <greearb@candelatech.com> wrote:
>
>
> 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

Re: CT and AP firmware not allowed beaconing in adhoc mode

[Adrian Chadd]

On 26 June 2014 00:40, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
> Not possible for all the modes to be supported in one single firmware?

It (mostly) is; it's a question of time, effort and resources.

There's a size limitation to how much code and data you can squeeze
into the firmware. Is it possible to structure the firmware in a way
that gives you one source tree for multiple firmware builds, with
different features on and off? Quite so.

That's just not how it happened inside of QCA. When I was working
there on the ath10k chip bringup, there indeed was one branch to do
station, adhoc and AP mode. That changed shortly after I left for
reasons I don't quite know. I'm still trying to .. well, figure out
how to try and repair that damage.



-a

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

Re: CT and AP firmware not allowed beaconing in adhoc mode

[Ben Greear]

On 06/26/2014 12:43 AM, Adrian Chadd wrote:
> On 26 June 2014 00:40, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
>> Not possible for all the modes to be supported in one single firmware?
>
> It (mostly) is; it's a question of time, effort and resources.
>
> There's a size limitation to how much code and data you can squeeze
> into the firmware. Is it possible to structure the firmware in a way
> that gives you one source tree for multiple firmware builds, with
> different features on and off? Quite so.
>
> That's just not how it happened inside of QCA. When I was working
> there on the ath10k chip bringup, there indeed was one branch to do
> station, adhoc and AP mode. That changed shortly after I left for
> reasons I don't quite know. I'm still trying to .. well, figure out
> how to try and repair that damage.

In my firmware, with 37 vdevs, I have maybe 2k of RAM left, but
55+k bytes of instruction ram (ie, where the program code can live left).

So, there is plenty of room for more code, and most people can get by with way
less than 37 vdevs, which saves both RAM and IRAM.

I am steadily improving RAM usage in CT firmware, mostly be naturally
packing structures, using bit shifting instead of uint32 for booleans, etc.

So, the code size is not the problem here....  Time and resources and the
fact we cannot share dev efforts with other developers due to NDA issues
is the main problem.

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