10 Jul, 2012

4 commits


05 Jul, 2012

2 commits

  • 60g band uses different from .11n MCS scheme, so bitrate
    should be calculated differently

    Signed-off-by: Vladimir Kondratiev
    Signed-off-by: Johannes Berg

    Vladimir Kondratiev
     
  • Until now, a u16 value was used to represent bitrate value.
    With VHT bitrates this becomes too small.

    Introduce a new 32-bit bitrate attribute. nl80211 will report
    both the new and the old attribute, unless the bitrate doesn't
    fit into the old u16 attribute in which case only the new one
    will be reported.

    User space tools encouraged to prefer the 32-bit attribute, if
    available (since it won't be available on older kernels.)

    Signed-off-by: Vladimir Kondratiev
    [reword commit message and comments a bit]
    Signed-off-by: Johannes Berg

    Vladimir Kondratiev
     

03 Jul, 2012

2 commits

  • Some drivers require setup before being able to send
    management frames in managed mode, in particular in
    multi-channel cases.

    Introduce API to allow the drivers to do such setup
    while being able to sleep waiting for the setup to
    finish in the device. This isn't possible inside the
    TX call since that can't sleep.

    A future patch may also restructure the TX retry to
    wait for the driver to report the frame status, as
    suggested by Arik in
    http://mid.gmane.org/CA+XVXffKSEL6ZQPQ98x-zO-NL2=TNF1uN==mprRyUmAaRn254g@mail.gmail.com

    Signed-off-by: Johannes Berg

    Johannes Berg
     
  • IEEE80211_TX_MAX_RATES can be reduced from 5 to 4 as there
    is no current hardware supporting a rate chain with 5 multi
    rate stages (mrr), so 4 mrr stages are sufficient.

    The memory that is freed within the ieee80211_tx_info struct
    will be used in the upcoming Transmission Power Control (TPC)
    implementation.

    Suggested-by: Felix Fietkau
    Signed-off-by: Thomas Huehn
    [reword commit message]
    Signed-off-by: Johannes Berg

    Thomas Huehn
     

02 Jul, 2012

3 commits


29 Jun, 2012

4 commits

  • We do not need it anymore since cfg80211 tracks
    monitor channel and monitor channel type.

    Signed-off-by: Michal Kazior
    Signed-off-by: Johannes Berg

    Michal Kazior
     
  • Implements .set_monitor_enabled(wiphy, enabled).

    Notifies driver upon change of interface layout.

    If only monitor interfaces become present it is
    called with 2nd argument being true. If
    non-monitor interface appears then 2nd argument
    is false. Driver is notified only upon change.

    This makes it more obvious about the fact that
    cfg80211 supports single monitor channel. Once we
    implement multi-channel we don't want to allow
    setting monitor channel while other interface
    types are running. Otherwise it would be ambiguous
    once we start considering num_different_channels.

    Signed-off-by: Michal Kazior
    Signed-off-by: Johannes Berg

    Michal Kazior
     
  • IBSS may hop between channels. It is necessary to
    account this special case when considering
    interface combinations.

    Signed-off-by: Michal Kazior
    Signed-off-by: Johannes Berg

    Michal Kazior
     
  • We need to know which channel is used by a running
    AP and mesh for channel context accounting and
    finding matching/active interface combination.

    STA/IBSS have current_bss already which allows us
    to check which channel a vif is tuned to.
    Non-fixed channel IBSS can be handled with
    additional changes.

    Monitor mode is going to be handled differently.

    Signed-off-by: Michal Kazior
    Signed-off-by: Johannes Berg

    Michal Kazior
     

28 Jun, 2012

5 commits


27 Jun, 2012

2 commits


26 Jun, 2012

1 commit


24 Jun, 2012

1 commit

  • There are a few things that make the logging and
    debugging in mac80211 less useful than it should
    be right now:
    * a lot of messages should be pr_info, not pr_debug
    * wholesale use of pr_debug makes it require *both*
    Kconfig and dynamic configuration
    * there are still a lot of ifdefs
    * the style is very inconsistent, sometimes the
    sdata->name is printed in front

    Clean up everything, introducing new macros and
    separating out the station MLME debugging into
    a new Kconfig symbol.

    Signed-off-by: Johannes Berg

    Johannes Berg
     

23 Jun, 2012

1 commit


21 Jun, 2012

2 commits


18 Jun, 2012

1 commit

  • As defined in section 13.10.9.3 Case D (802.11-2012), this
    control variable is used to limit the mesh STA to send only
    one PREQ to a root mesh STA within this interval of time
    (in TUs). The default value for this variable is set to
    2000 TUs. However, for current implementation, the maximum
    configurable of dot11MeshHWMPconfirmationInterval is
    restricted by dot11MeshHWMPactivePathTimeout.

    Signed-off-by: Chun-Yeow Yeoh
    [line-break commit log]
    Signed-off-by: Johannes Berg

    Chun-Yeow Yeoh
     

14 Jun, 2012

5 commits


13 Jun, 2012

2 commits


12 Jun, 2012

2 commits


11 Jun, 2012

2 commits


09 Jun, 2012

1 commit