Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapt to AP rates and enable n-rates #54

Merged
merged 6 commits into from Jun 18, 2013

Conversation

Coi-l
Copy link
Contributor

@Coi-l Coi-l commented Jun 13, 2013

The goal of this patch set is twofold.

  1. I wanted to adapt the rates the STA used to be based
    on the intersection of rates between the AP and STA.
    Up until now, we've sent ofdm-rates to b-only APs.
    Enabling n-rates would make this worse.

  2. I wanted to enable n-rates

Change the name of the rates table to something more appropriate.
llb and lla (yes.. lowercase L) are not that descriptive, especially
since lla was used for 2.4GHz action as well.

Signed-off-by: Olof Johansson <dev@skyshaper.net>
These will need to be accessed in different places across the file.
Move them to the beginning of the file for easy access.

Signed-off-by: Olof Johansson <dev@skyshaper.net>
The hardware expects these values in the rates table sent to them.
Let's use them here for easy access later.

Signed-off-by: Olof Johansson <dev@skyshaper.net>
These are not legacy rates but the rates used on 2.4GHz. Naming now
also better matches the rate table for 5GHz.

Signed-off-by: Olof Johansson <dev@skyshaper.net>
This function will set the set of rates allowed for this access point
before the rates are sent to the firmware.

Signed-off-by: Olof Johansson <dev@skyshaper.net>
This will enable n-rates on access points with support for n-rates.

Signed-off-by: Olof Johansson <dev@skyshaper.net>
KrasnikovEugene added a commit that referenced this pull request Jun 18, 2013
Adapt to AP rates and enable n-rates
@KrasnikovEugene KrasnikovEugene merged commit e82a7d0 into KrasnikovEugene:master Jun 18, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants