[rt2x00-users] [PATCH] Rt2x00 - Fix the interval for rfkill and link_tuner.
prahal at yahoo.com
Mon Apr 20 14:50:54 CDT 2009
Le lundi 20 avril 2009 à 21:42 +0200, Alban Browaeys a écrit :
> extra parenthesis made the value an argument and the value of the
> define empty.
> This was triggering those very fast.
> Signed-off-by: Alban Browaeys <prahal at yahoo.com>
> drivers/net/wireless/rt2x00/rt2x00lib.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
> diff --git a/drivers/net/wireless/rt2x00/rt2x00lib.h b/drivers/net/wireless/rt2x00/rt2x00lib.h
> index ccc7ba4..39e00b3 100644
> --- a/drivers/net/wireless/rt2x00/rt2x00lib.h
> +++ b/drivers/net/wireless/rt2x00/rt2x00lib.h
> @@ -32,8 +32,8 @@
> * Interval defines
> * Both the link tuner as the rfkill will be called once per second.
> -#define LINK_TUNE_INTERVAL ( round_jiffies_relative(HZ) )
> -#define RFKILL_POLL_INTERVAL ( 1000 )
> +#define LINK_TUNE_INTERVAL round_jiffies_relative(HZ)
> +#define RFKILL_POLL_INTERVAL 1000
> * rt2x00_rate: Per rate device information
forgot to tell this fix rfkill_input breakage . That is rfkill was
freezing : write error : Operation not permitted when trying to write to
any of the rkill state file (bluetooth too). Needed a modprobe -r then
modprobe of rfkill_input to get thinks back beforehand.
Guess this was because rfkill was trying to spawn the poll faster than
light (my logs were not showing any call of it except the first one
though the other rfkill being stuck lead me to think that way).
More information about the users