- 11 Sep, 2008 1 commit
-
-
Dan Williams authored
If certain commands were in-flight when the card was pulled or the driver rmmod-ed, cleanup would block on the work queue stopping, but the work queue was in turn blocked on the current command being canceled, which didn't happen. Fix that. Signed-off-by:
Dan Williams <dcbw@redhat.com> Cc: stable <stable@kernel.org> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
- 29 Aug, 2008 4 commits
-
-
Dan Williams authored
with fixes for v9 and later firmware too. Signed-off-by:
-
Dan Williams authored
and return errors for operations like join & scan that aren't possible when the radio is turned off. Signed-off-by:
-
Dan Williams authored
and remove DISASSOCIATE because it's not in any of the specs and has never been used. Signed-off-by:
-
Dan Williams authored
And while we're at it, grab min/max TX power from the firmware and use that to validate incoming TX power requests from WEXT. Signed-off-by:
-
- 01 Aug, 2008 1 commit
-
-
Dan Williams authored
Since only mesh-enabled firmware has the CMD_802_11_MONITOR_MODE on which the rtap functionality depends, only expose the rtap functionality when mesh is also available. Signed-off-by:
-
- 15 Jul, 2008 2 commits
-
-
David S. Miller authored
Now that we have a specific lock to protect the network device unicast and multicast lists, remove extraneous grabs of the TX lock in cases where the code only needs address list protection. Signed-off-by:David S. Miller <davem@davemloft.net>
-
David S. Miller authored
Add netif_addr_{lock,unlock}{,_bh}() helpers. Use them to protect operations that operate on or read the network device unicast and multicast address lists. Also use them in cases where the code simply wants to block calls into the driver's ->set_rx_mode() and ->set_multicast_list() methods. Signed-off-by:
-
- 09 Jun, 2008 1 commit
-
-
Holger Schurig authored
This fixes an issus that made "iwconfig eth1 power on" non-working. When we get a "PS sleep" event, we have to confirm this to the firmware. The confirm happens with a command, but this command is special: the firmware won't send us a response. if_cs_host_to_card() is setting priv->dnld_sent anyway, so this variable stayed at DNLD_DATA_SENT and was never cleared back. Now I put the special knowledge that the CMD_802_11_PS_MODE with CMD_SUBCMD_SLEEP_CONFIRMED doesn't need to need a response by directly clearing the dnld_sent state in lbs_send_confirmsleep(). Signed-off-by:
Holger Schurig <hs4233@mail.mn-solutions.de> Acked-by:
-
- 03 Jun, 2008 3 commits
-
-
Javier Cardona authored
Implemented rate adaptation support via 'iwconfig rate' API. It is now possible to specify a bit-rate value and append 'auto'. That will configure rate adaptation to use all bit-rates equal or lower than than selected value. Made lbs_cmd_802_11_rate_adapt_rateset a direct command. Signed-off-by:
Javier Cardona <javier@cozybit.com> Signed-off-by:
David Woodhouse <dwmw2@infradead.org> Acked-by:
-
Holger Schurig authored
If we don't check for a command response early, but rather sleep, then we might sleep despite an already-received command response. This will lead to a command-timeout. Signed-off-by:
-
Holger Schurig authored
priv->driver_lock has already been unlocked some lines above. This patch fixes the sparse warning: drivers/net/wireless/libertas/main.c:792:6: warning: context problem in 'lbs_thread': '_spin_unlock_irq' expected different context drivers/net/wireless/libertas/main.c:792:6: context 'lock': wanted >= 1, got 0 Signed-of-by:
-
- 21 May, 2008 5 commits
-
-
Holger Schurig authored
[PATCH, take 2] libertas: reduce command retry time In the normal case, an unsuccessful command would be retried for 10*5 seconds, or 10*10 seconds in the worst case. This patch reduces this to 3*3 seconds, or 3*10 seconds in the worst case. I also reduced the time it takes to start a new command downloaded. Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
Javier Cardona authored
This will create the following sysfs directories: /sys/class/net/mshX ... |-- boot_options | |-- bootflag | `-- boottime ... |-- mesh_ie | |-- capability | |-- mesh_id | |-- metric_id | `-- protocol_id Signed-off-by:
-
Javier Cardona authored
This patch is based on a patch from Shailendra Govardhan and Brian Cavagnolo. It extends the MESH_CONFIG command to configure non-volatile parameters on libertas devices that support them (e.g. OLPC Active Antenna). This patch only implements the driver/firmware interface. See http://dev.laptop.org/ticket/6823 for minimal testing results and known issues. Signed-off-by:
-
David Woodhouse authored
We weren't properly handling multicast on the mesh interface. Fix that, which involves setting up the hardware to use the union of dev->mc_list for both eth%d and msh%d devices. This means we can't do it directly from ->set_multicast_list() because we'd need to lock the other device to read its list, and we can't do that because it might deadlock. So punt the actual work to keventd. Also, invoke the same when taking an interface down; for some reason the core calls ->set_multicast_list while IFF_UP is still set in dev->flags when we're taking it down, so its addresses don't get removed then. We also convert MAC_MULTICAST_ADR to a direct command while we're at it, removing one more entry from the big switch statement in the deprecated lbs_prepare_and_send_command() function. Signed-off-by:
-
- 16 May, 2008 2 commits
-
-
Masakazu Mokuno authored
Some network interfaces of the wireless drivers lack the 'device' symlink in sysfs. This patch lets the drivers create the links. Signed-off-by:
Masakazu Mokuno <mokuno@sm.sony.co.jp> Acked-by:
-
Brian Cavagnolo authored
This is a fix for OLPC ticket #6586: "SCAN command fails, timer doesn't fire". In fact, the timer was firing; the problem was that the dnld_sent state variable was not being updated after the timer expired, so lbs_execute_next_command was not being called. Signed-off-by:
Brian Cavagnolo <brian@cozybit.com> Signed-off-by:
-
- 14 May, 2008 1 commit
-
-
Holger Schurig authored
lbs_get_data_rate() gets called, but no-one uses it's result. Signed-off-by:
-
- 07 May, 2008 3 commits
-
-
Holger Schurig authored
This fixes several problems I had: * when removing the card while the card was scanning or associtating, it could happen that destroy_workqueue() stuck and didn't return. * make sure the command function doesn't run while we remove the list of pending commands * for still unknown reason, I had calls to lbs_stop_card() with priv==NULL Signed-off-by:
-
Holger Schurig authored
They don't return anything meaningfull and no-one cares about their results. Signed-off-by:
-
Holger Schurig authored
* make debug output match the variable name * always report that lbs_remove_rtap() has has been exited Signed-off-by:
-
- 16 Apr, 2008 1 commit
-
-
Holger Schurig authored
This patch (co-developed by Dan Williams and Holger Schurig) uses a kfifo object for events and a swapping buffer scheme for the command response to preserve the zero-copy semantics of the CF driver and keep memory usage low. The main thread should only ever touch the buffer indexed by priv->resp_idx, while the interface code is free to write to the second buffer, then swap priv->resp_idx under the driver spinlock. The firmware specs only permit one in-flight command, so there will only ever be one command response to process at a time. Signed-off-by:
-
- 08 Apr, 2008 2 commits
-
-
Holger Schurig authored
Besides code moving, I did the following changes: * made some functions static * removed some unneeded #include's * made patch checkpatch.pl clean Signed-off-by:
-
Holger Schurig authored
Besides code moving, I did the following changes: * made some functions static * removed some unneeded #include's * made patch checkpatch.pl clean Signed-off-by:
-
- 01 Apr, 2008 3 commits
-
-
Holger Schurig authored
Runtime-wise we only need escape_ssid from the deprecated IEEE80211 subsystem. However, it's easy to provide our own copy. Signed-off-by:
-
Holger Schurig authored
Confirm sleep event: they come very regularly, eventually several times per second. Therefore we want to send the config command as fast as possible. The old code pre-set the command in priv->lbs_ps_confirm_sleep. However, the byte sequence to be sent to the hardware is the same for all interfaces. So this patch make this an extern structure, initialized at module load time. Config wake event: normal conversion to a direct command. However, I don't know how to trigger a "HOST AWAKE" event from the firmware, so this part is untested. Signed-off-by:
-
Holger Schurig authored
* directly call lbs_cmd_with_response() * only overwrite priv->current_addr once the firmware call succeeded Signed-off-by:
-
- 27 Mar, 2008 1 commit
-
-
Holger Schurig authored
Signed-off-by:
-
- 25 Mar, 2008 3 commits
-
-
Holger Schurig authored
This removes many unused function parameters as well as some not-implemented functions, e.g. CMD_802_11_GET_STATS. The silly lbs_set_cmd_ctrl_node() function is now also gone. Signed-off-by:
-
Holger Schurig authored
* firmware for the CF card supports power saving * the driver currenly only accept "iwconfig ethX power on|off", so I fixed what the range wext ioctl reports. * initialize value/flags in lbs_get_power() * get rid of unused parameter psmode in lbs_ps_confirm_sleep() * some minor debug output tweaks Signed-off-by:
-
Holger Schurig authored
The CMD_MAC_CONTROL can be used for other things than just filtering packets, e.g. to enable and disable WMM. This uses the same term mac_control for the define, the function and the shadow value in struct lbs_private. Signed-off-by:
-
- 29 Feb, 2008 1 commit
-
-
Holger Schurig authored
... by moving it into the file where it's sole user resides Signed-off-by:
-
- 28 Feb, 2008 1 commit
-
-
Roland Dreier authored
The libertas driver exports a number of symbols with no in-tree users; remove these unused exports. lbs_reset_device() is completely unused, with no callers at all, so remove the function completely. A couple of these unused exported symbols are static, which causes the following build error on ia64 with gcc 4.2.3: drivers/net/wireless/libertas/main.c:1375: error: __ksymtab_lbs_remove_mesh causes a section type conflict drivers/net/wireless/libertas/main.c:1354: error: __ksymtab_lbs_add_mesh causes a section type conflict Signed-off-by:Roland Dreier <rolandd@cisco.com> Acked-by:
-
- 28 Jan, 2008 5 commits
-
-
Holger Schurig authored
libertas: re-pepper debug statementThe recent fluff of updates didn't put proper lbs_deb_enter/leave calls into the source code. Add them where appropriate. Also contains some whitespace changes. Signed-off-by:
-
Holger Schurig authored
The CF card only has a very old firmware (5.0.16p0). This firmware doesn't know anything about mesh config. However, current code blindly calls mesh_config when the card is inserted. So check the firmware version before issuing this command. Signed-off-by:
-
David Woodhouse authored
Signed-off-by:
-
David Woodhouse authored
We don't necessarily want to reset the device on a TX timeout. But more often than not, the real cause is that the firmware has crapped itself, not just that the network is busy. So submit any harmless command, and if _that_ times out, then the error handling code will reset the module, as appropriate. Signed-off-by:
-
David Woodhouse authored
And handle the case where it times out more than once, too, instead of locking up for ever. Signed-off-by:
-
