Re: [ath5k-devel] [PATCH 1/1] ath5k: fix beacon_int handling

2009-06-18 Thread Bob Copeland
On Thu, Jun 18, 2009 at 9:14 PM, Bob Copeland wrote: >> Otherwise it will be set only once by upper layer through >> bss_info_changed but not on second and further hostap executions. > > Shouldn't we just not destroy the value in add_interface? Err, nevermind, that's exactly what your patch does.

Re: [ath5k-devel] [PATCH 1/1] ath5k: fix beacon_int handling

2009-06-18 Thread Bob Copeland
On Thu, Jun 18, 2009 at 7:06 PM, Jiri Slaby wrote: > 73ca5203366235f8a43e490767284ba8cfd8c479 > (ath5k: remove conf->beacon_int usage) > removed bintval setting from ath5k_config. We need to init the > interval earlier and don't touch it in add_interface anymore. > > Otherwise it will be set only o

[ath5k-devel] [PATCH 1/1] ath5k: fix beacon_int handling

2009-06-18 Thread Jiri Slaby
73ca5203366235f8a43e490767284ba8cfd8c479 (ath5k: remove conf->beacon_int usage) removed bintval setting from ath5k_config. We need to init the interval earlier and don't touch it in add_interface anymore. Otherwise it will be set only once by upper layer through bss_info_changed but not on second