diff options
| author | Inaky Perez-Gonzalez <inaky@linux.intel.com> | 2009-10-03 16:51:02 +0900 |
|---|---|---|
| committer | Inaky Perez-Gonzalez <inaky@linux.intel.com> | 2009-10-19 15:56:14 +0900 |
| commit | 81d3f905389e22bb9a5176b9309c3f451c260e1a (patch) | |
| tree | 8b7cc14d8c19d63f4d7a3e1d38cf49defc769620 /net/ethernet | |
| parent | de9315fa3a35ebe587cc1a1c88655d095846785e (diff) | |
| download | op-kernel-dev-81d3f905389e22bb9a5176b9309c3f451c260e1a.zip op-kernel-dev-81d3f905389e22bb9a5176b9309c3f451c260e1a.tar.gz | |
wimax: allow WIMAX_RF_QUERY calls when state is still uninitialized
Until now, calls to wimax_rfkill() will be blocked until the device is
at least past the WIMAX_ST_UNINITIALIZED state, return -ENOMEDIUM when
the device is in the WIMAX_ST_DOWN state.
In parallel, wimax-tools would issue a wimax_rfkill(WIMAX_RF_QUERY)
call right after opening a handle with wimaxll_open() as means to
verify if the interface is really a WiMAX interface [newer kernel
version will have a call specifically for this].
The combination of these two facts is that in some cases, before the
driver has finalized initializing its device's firmware, a
wimaxll_open() call would fail, when it should not.
Thus, change the wimax_rfkill() code to allow queries when the device
is in WIMAX_ST_UNINITIALIZED state.
Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Diffstat (limited to 'net/ethernet')
0 files changed, 0 insertions, 0 deletions
