Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 160
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 06 6月, 2012 2 次提交
  3. 17 5月, 2012 1 次提交
  5. 16 5月, 2012 1 次提交
  7. 09 5月, 2012 5 次提交
  9. 13 4月, 2012 1 次提交
  11. 08 3月, 2012 3 次提交
  13. 02 2月, 2012 1 次提交
  15. 25 1月, 2012 1 次提交
  17. 07 1月, 2012 1 次提交
  19. 09 12月, 2011 3 次提交
  21. 09 11月, 2011 1 次提交
  23. 15 10月, 2011 1 次提交
  25. 12 10月, 2011 1 次提交
  27. 20 9月, 2011 1 次提交
  29. 15 9月, 2011 1 次提交
  31. 30 8月, 2011 4 次提交
  33. 09 8月, 2011 1 次提交
  35. 21 7月, 2011 7 次提交
    • J
      iwlagn: implement WoWLAN · c8ac61cf
      由 Johannes Berg 提交于 
      Implement WoWLAN support in iwlagn. The device
supports a number of wakeup triggers and can do
GTK rekeying when asleep (if HW crypto is used).
Unfortunately, we need to disconnect from the AP
after resume since we can't yet get all the info
out of the wowlan uCode to stay connected safely.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      c8ac61cf
    • J
      iwlagn: rewrite HW crypto · 5a3d9882
      由 Johannes Berg 提交于 
      As I just discovered while doing WoWLAN, HW crypto
is done wrong for GTKs: they should be programmed
for the AP station ID (in the managed mode case)
and the HW can actually deal with multiple group
keys per station as well (which is useful in IBSS
RSN but that I've chosen not to use this).

To fix all this, modify the way keys are sent to
the device and key offsets are allocated. After
these changes, key offsets are stored into the
hw_key_idx which we can then track for the key
lifetime, not relying on our sta_cmd array. WEP
default keys get special treatment, of course.

Additionally, since I had the API for it, we can
now pre-fill TKIP phase 1 keys for RX now that we
can obtain the P1K from mac80211, a capability I
had added for WoWLAN initially.

Finally, some keys simply don't need to be added
into the device's key cache -- a key that won't
be used for RX is only needed in the TX header,
so "pretend" to have accepted any key without
adding it into the device -- no need to use up
key space there for it.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      5a3d9882
    • W
      iwlagn: radio sensor offset in le16 format · 2e277996
      由 Wey-Yi Guy 提交于 
      For temperature offset calibration, send radio sensor offset in le16 format
Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      2e277996
    • W
      iwlagn: define valid init calibration mask · ad3f7124
      由 Wey-Yi Guy 提交于 
      Use the valid calibration mask for init calibration
Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      ad3f7124
    • W
      iwlagn: remove legacy calibration command · a21321c1
      由 Wey-Yi Guy 提交于 
      IWL_PHY_CALIBRATE_DIFF_GAIN_CMD is for legacy device, remove it
Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      a21321c1
    • W
      iwlagn: set correct calibration flag · df2a4dc8
      由 Wey-Yi Guy 提交于 
      Set calibration config flag for complete notification
Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      df2a4dc8
    • P
      treewide: fix potentially dangerous trailing ';' in #defined values/expressions · 497888cf
      由 Phil Carmody 提交于 
      All these are instances of
  #define NAME value;
or
  #define NAME(params_opt) value;

These of course fail to build when used in contexts like
  if(foo $OP NAME)
  while(bar $OP NAME)
and may silently generate the wrong code in contexts such as
  foo = NAME + 1;    /* foo = value; + 1; */
  bar = NAME - 1;    /* bar = value; - 1; */
  baz = NAME & quux; /* baz = value; & quux; */

Reported on comp.lang.c,
Message-ID: <ab0d55fe-25e5-482b-811e-c475aa6065c3@c29g2000yqd.googlegroups.com>
Initial analysis of the dangers provided by Keith Thompson in that thread.

There are many more instances of more complicated macros having unnecessary
trailing semicolons, but this pile seems to be all of the cases of simple
values suffering from the problem. (Thus things that are likely to be found
in one of the contexts above, more complicated ones aren't.)
Signed-off-by: NPhil Carmody <ext-phil.2.carmody@nokia.com>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      497888cf
  37. 16 7月, 2011 1 次提交
  39. 12 7月, 2011 1 次提交
    • M
      iwlagn: Enable/disable PS poll based on RSSI and BT coex traffic state · 207ecc5e
      由 Meenakshi Venkataraman 提交于 
      WiFi throughput drops drastically when BT is turned on, BT and WiFi
are simultaneously transmitting/receiving traffic. This is particularly true
when BT has higher priority over WiFi, and hence the device defers TX frames.
The AP assumes that the channel is bad and reduces the data rate, implying
longer airtime, which exacerbates the problem further, resulting ultimately
in what is popularly called the "death-spiral" phenomenon. The use of PS-poll
in such scenarios guarantees a low but consistent throughput.

Since the death-spiral phenomenon is observed only when the RSSI is low, use
PS-poll only when RSSI is low and disable when high, with a known hysterisis.

This feature specifies the high and low thresholds and implements the
callbacks registered with mac80211, which will be called when threshold events
occur.

iwlwifi: dynamic pspoll: optimize rssi monitor code
Signed-off-by: NMeenakshi Venkataraman <meenakshi.venkataraman@intel.com>
Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      207ecc5e
  41. 18 6月, 2011 2 次提交