On Mon, 2013-02-18 at 16:07 +0100, Marco Porsch wrote:
I guess you can tell I'm not in a good mood today. I think any use of
get_tsf() for operation is a complete waste of time, there's no way you
can get the timings correct. You could be preempted, and suddenly sleep
for a few tens or
Move the beacon handler into mesh_neighbour_update where the STA
pointer is already available. This avoids additional overhead
and simplifies the handler.
The repositioning will also benefit mesh PS which uses T_r and
the updated T_offset value.
Rename the handler to better reflect its purpose.
Configure the HW for PS mode if the local mesh PS parameters
allow so.
Expose a callback ieee80211_mps_init for drivers to register
mesh powersave ops:
- hw_doze - put the radio to sleep now, wake up at given TBTT
- hw_wakeup - wake the radio up for frame RX
These ops may be extended in the
On Monday, February 18, 2013 05:08:28 PM Marco Porsch wrote:
---
+/**
+ * ieee80211_mps_sta_tbtt_update - update peer beacon wakeup schedule
+ *
+ * @sta: mesh STA
+ * @mgmt: beacon frame
+ * @tim: TIM IE of beacon frame
+ * @tsf_local: current HW TSF
+ */
+void
Hi all, there is some kind of regression with setting transmit power, hardware
is warious
ar9280 cards, all work as sould with compat-wireless-3.6 and compat-drivers-2013-02-13, i
have modified regulatory database:
iw reg get
country RU:
(2402 - 2494 @ 40), (24, 23)
(5030 - 5835 @
On 2013-02-19 04:04 +0400, Georgiewskiy Yuriy wrote linux-wirel...@vger.ker...:
hm, update - on 3.8.0 all ok
GY
GYHi all, there is some kind of regression with setting transmit power,
GYhardware is warious
GYar9280 cards, all work as sould with compat-wireless-3.6 and
