diff options
| author |   Wolfram Sang <wsa@the-dreams.de> | 2016-06-17 10:46:52 +0200 |
|---|---|---|
| committer |   Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2016-06-18 19:45:55 -0700 |
| commit | 6ee9169b407f70334f59cdf5a40a72a5d27f0ec2 (patch) | |
| tree | a4daeee84cb8b28aa23f8e6ae4abe6d135c36fc7 /drivers/staging/ks7010/TODO | |
| parent | staging/android: sync_debug: unproxify debugfs files' fops (diff) | |
| download | linux-dev-6ee9169b407f70334f59cdf5a40a72a5d27f0ec2.tar.xz linux-dev-6ee9169b407f70334f59cdf5a40a72a5d27f0ec2.zip | |
staging: ks7010: remove cfg file handling
I verified that all but two settings from the config file can be set up
also via 'iwconfig' or 'iwpriv'. The two missing are ROM_FILE and
PhyInformationTimer. ROM_FILE can be easily dropped. There is only one
known firmware floating on the net, so, the name is fix and we can make
this constant. Frankly, I don't know when PhyInformationTimer needs to
be set to non-zero. But if we need it somewhen, there is already
(currently commented out) code to add this as another private method, so
we could use that. Summa summarum: We can remove the config file
handling and the example config file. The only useful action,
initialization of the configuration struct, is now moved to the sdio
main file.
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/ks7010/TODO')
| -rw-r--r-- | drivers/staging/ks7010/TODO | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/staging/ks7010/TODO b/drivers/staging/ks7010/TODO index 5cbb4ca99974..2938d35be5bb 100644 --- a/drivers/staging/ks7010/TODO +++ b/drivers/staging/ks7010/TODO @@ -26,7 +26,6 @@ Now the TODOs: - fix codechecker warnings (checkpatch, sparse, smatch). But PLEASE make sure that you are not only silencing the warning but really fixing code. You should understand the change you submit. -- drop using a config file and use an upstream technique for configuration - fix the 'card removal' event when card is inserted when booting - check what other upstream wireless mechanisms can be used instead of the custom ones here |