[ath9k-devel] [help appreciated!] What section(s) of the ath9k source code can I change...

[ath9k-devel] [help appreciated!] What section(s) of the ath9k source code can I change...

[Jay Davidson]

Hi all,

I was told that I can't change the Modulation Scheme 0-15 (MCS), Frame
aggregation (MPDU/MSDU) size without patching source code.

So I would be grateful if someone could outline which sections of the ath9k
source code I would need to modify(patch) in order to be able to change the
above features.

Also does ath9k have a way of activating spacial divison multiplexing(SDM)
as well as the other .11n MIMO features, and is their a chipset (AR9XXX)
that supports 450Mbits/s phy /300Mbits/s TCP/IP in the ATH9K driver.

Thank you all very much
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20101116/6aac1937/attachment.htm 

[ath9k-devel] [help appreciated!] What section(s) of the ath9k source code can I change...

[Jay Davidson]

Hi all,

Can someone please advise asap regrading my previous question.

Thanks

On Tue, Nov 16, 2010 at 10:46 PM, Jay Davidson <jdiq123@googlemail.com>wrote:

> Hi all,
>
> I was told that I can't change the Modulation Scheme 0-15 (MCS), Frame
> aggregation (MPDU/MSDU) size without patching source code.
>
> So I would be grateful if someone could outline which sections of the ath9k
> source code I would need to modify(patch) in order to be able to change the
> above features.
>
> Also does ath9k have a way of activating spacial divison multiplexing(SDM)
> as well as the other .11n MIMO features, and is their a chipset (AR9XXX)
> that supports 450Mbits/s phy /300Mbits/s TCP/IP in the ATH9K driver.
>
> Thank you all very much
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20101202/30ad852a/attachment.htm 

[ath9k-devel] [help appreciated!] What section(s) of the ath9k source code can I change...

[Adrian Chadd]

The transmit side code is in xmit.c. That takes care of building up
the TX descriptor list, handling A-MPDU assembly, etc.

The MCS rates are selected by the rate mechanism in net80211. There's
code in xmit.c which assembles the 11n rate scenario array and
populates it with the TX rate for each of the four scenarios. It then
calls MAC specific calls (for <ar9003 and => ar9003 chips) which
writes this into the TX descriptor.

If you'd like to twiddle the selected MCS rates, you'd likely need to
look at the net80211 code and the TX rate control/selection algorithm
used.

HTH,


Adrian

On 3 December 2010 07:46, Jay Davidson <jdiq123@googlemail.com> wrote:
> Hi all,
>
> Can someone please advise asap regrading my previous question.
>
> Thanks
>
> On Tue, Nov 16, 2010 at 10:46 PM, Jay Davidson <jdiq123@googlemail.com>
> wrote:
>>
>> Hi all,
>>
>> I was told that I can't change the Modulation Scheme 0-15 (MCS), Frame
>> aggregation (MPDU/MSDU) size without patching source code.
>>
>> So I would be grateful if someone could outline which sections of the
>> ath9k source code I would need to modify(patch) in order to be able to
>> change the above features.
>>
>> Also does ath9k have a way of activating spacial divison multiplexing(SDM)
>> as well as the other .11n MIMO features, and is their a chipset (AR9XXX)
>> that supports 450Mbits/s phy /300Mbits/s TCP/IP in the ATH9K driver.
>>
>> Thank you all very much
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>