- 19 Oct, 2009 17 commits
-
-
Dirk Brandewie authored
In i2400m-based devices, the driver's bootloader will retry to load the firmware when things go wrong. The driver currently has a constant (I2400M_BOOT_RETRIES) which governs the max number of tries. However, different SKUs of the same hardware may admit or require different numbers of retries due to it's particulars, so it is made a BUS specific parameter and different values are assigned for 5x50 devices versus the 3200 ones. Signed-off-by:
Dirk Brandewie <dirk.j.brandewie@intel.com> Signed-off-by:
Cindy H Kao <cindy.h.kao@intel.com> Signed-off-by:
Inaky Perez-Gonzalez <inaky@linux.intel.com>
-
Dirk Brandewie authored
The change to the SDIO boot mode RX chain could try to use the cmd and ack buffers befor they were allocated. USB does not have the problem but both were changed for consistency's sake. Signed-off-by:
-
Dirk Brandewie authored
Fixing comments from original cut and paste error Signed-off-by:
-
Dan Williams authored
Add minimal ethtool support for carrier detection. Signed-off-by:
Dan Williams <dcbw@redhat.com> Signed-off-by:
-
Roel Kluin authored
Fix misplaced parenthesis Signed-off-by:
Roel Kluin <roel.kluin@gmail.com> Signed-off-by:
-
Roel Kluin authored
Ensure that index `status' remains within ms_to_errno[] Signed-off-by:
-
Inaky Perez-Gonzalez authored
The WiMAX stack assumes that all WiMAX devices are SW OFF when they are initialized. The recent changes in the RFKILL stack thus cause an initial call after rfkill_register(), because by default, rfkill considers devices to be SW ON upon registration. So call rfkill_init_sw_state() to set it to SW OFF so rfkill_register() doesn't do that unnecessary step. Signed-off-by: -
Cindy H Kao authored
i2400ms_bus_bm_wait_for_ack() causes a race condition. It happens because this function clears i2400ms->bm_ack_size before waiting for an interrupt, which is set by the interrupt service routine i2400ms_rx() to indicate reception and size of received data; thus, if the interrupt came right before the clearing/waiting, it is lost. The fix is clear the bm_ack_size to -EINPROGRESS before we are enabling the RX interrupt configuration in i2400ms_rx_setup(). Then everytime when the interrupt service routine i2400ms_rx() is invoked during bootmode, bm_ack_size is updated with the actual rx_size and it is cleared to -EINPROGRESS again after the RX data is handled. Signed-off-by:
-
Oliver Neukum authored
This patch removes an unneeded power management primitive. Power management is automatically enabled as probe ends. Signed-off-by:
Oliver Neukum <oliver@neukum.org> Signed-off-by:
-
Steffen Klassert authored
The last users of skb_icv_walk are converted to ahash now, so skb_icv_walk is unused and can be removed. Signed-off-by:
Steffen Klassert <steffen.klassert@secunet.com> Signed-off-by:
David S. Miller <davem@davemloft.net>
-
Steffen Klassert authored
ah4 and ah6 are converted to ahash now, so we can remove the code for the obsolete hash algorithm. Signed-off-by:
-
Steffen Klassert authored
This patch converts ah6 to the new ahash interface. Signed-off-by:
-
Steffen Klassert authored
This patch converts ah4 to the new ahash interface. Signed-off-by:
-
Steffen Klassert authored
To support for ahash algorithms, we add a pointer to a crypto_ahash to ah_data. Signed-off-by:
-
Alan Cox authored
Signed-off-by:
Alan Cox <alan@linux.intel.com> Signed-off-by:
-
Eric Dumazet authored
- skb_kill_datagram() can increment sk->sk_drops itself, not callers. - UDP on IPV4 & IPV6 dropped frames (because of bad checksum or policy checks) increment sk_drops Signed-off-by:
Eric Dumazet <eric.dumazet@gmail.com> Signed-off-by:
-
Eric Dumazet authored
In order to have better cache layouts of struct sock (separate zones for rx/tx paths), we need this preliminary patch. Goal is to transfert fields used at lookup time in the first read-mostly cache line (inside struct sock_common) and move sk_refcnt to a separate cache line (only written by rx path) This patch adds inet_ prefix to daddr, rcv_saddr, dport, num, saddr, sport and id fields. This allows a future patch to define these fields as macros, like sk_refcnt, without name clashes. Signed-off-by:
-
- 18 Oct, 2009 15 commits
-
-
Krishna Kumar authored
1. GENL_MIN_ID is a valid id -> no need to start at GENL_MIN_ID + 1. 2. Avoid going through the ids two times: If we start at GENL_MIN_ID+1 (*or bigger*) and all ids are over!, the code iterates through the list twice (*or lesser*). 3. Simplify code - no need to start at idx=0 which gets reset to GENL_MIN_ID. Patch on net-next-2.6. Reboot test shows that first id passed to genl_register_family was 16, next two were GENL_ID_GENERATE and genl_generate_id returned 17 & 18 (user level testing of same code shows expected values across entire range of MIN/MAX). Signed-off-by:
Krishna Kumar <krkumar2@in.ibm.com> Signed-off-by:
-
Krishna Kumar authored
genl_register_family() doesn't need to call genl_family_find_byid when GENL_ID_GENERATE is passed during register. Patch on net-next-2.6, compile and reboot testing only. Signed-off-by:
-
Krishna Kumar authored
The xmit handler doesn't need to wake the queue after stopping it temporarily (some other drivers are doing the same). Patch on net-next-2.6, multiple netperf sessions tested. Signed-off-by:
Divy Le Ray <divy@chelsio.com> Signed-off-by:
-
Einar Lueck authored
Group device now cleanly reacts to failures during channel start and implements a clean rollback. Signed-off-by:
Einar Lueck <elelueck@de.ibm.com> Signed-off-by:
Ursula Braun <ursula.braun@de.ibm.com> Signed-off-by:
-
Klaus-Dieter Wacker authored
The creation of a new lcs device requires a call to the function ccw_device_set_online() for the read and the write channel. Failure of either call should terminate the lcs device creation immediately with return code -ENODEV. Signed-off-by:
Klaus-Dieter Wacker <kdwacker@de.ibm.com> Signed-off-by:
-
Klaus-Dieter Wacker authored
Timer_list structure in lcs_send_lancmd() is allocated on stack. Initialization with init_timer() leads to above ODEBUG message. Instead use init_timer_on_stack() which prevents above msg. Signed-off-by:
-
Ursula Braun authored
Remove duplicate sock_set_flag(sk, SOCK_ZAPPED) in iucv_sock_close, which has been overlooked in September-commit 7514bab0. Cc: Hendrik Brueckner <brueckner@linux.vnet.ibm.com> Signed-off-by:
-
Hendrik Brueckner authored
Instead of modifying sk->sk_ack_backlog directly, use respective socket functions. Signed-off-by:
Hendrik Brueckner <brueckner@linux.vnet.ibm.com> Signed-off-by:
-
Dhananjay Phadke authored
Signed-off-by:
Dhananjay Phadke <dhananjay@netxen.com> Signed-off-by:
-
Narender Kumar authored
Firmware hang detection and recovery (reset) need to be disabled for diagnostic tools, which can run some disruptive tests. This adds a driver level control to turn off this feature by diag tools. Signed-off-by:
Narender Kumar <narender.kumar@qlogic.com> Signed-off-by:
-
Dhananjay Phadke authored
Use -EIO or -EINVAL as error codes, these can get passed up to applications (tools). Signed-off-by:
-
Amit Kumar Salecha authored
Add support for different windowing scheme for on chip memory in future chip revisions. This is required by diagnostic tools. Signed-off-by:
Amit Kumar Salecha <amit@netxen.com> Signed-off-by:
-
Amit Kumar Salecha authored
Future revisions need different chip reset sequence and firmware initialization. Also clean up some never used debug code. Signed-off-by:
-
Amit Kumar Salecha authored
Future revisions of the chip have 128 bit memory transactions. Require drivers to implement rmw in case of sub-128 bit accesses by driver. This is mostly used by diagnostic tools. Signed-off-by:
-
Amit Kumar Salecha authored
Signed-off-by:
-
- 17 Oct, 2009 1 commit
-
-
Ajit Khaparde authored
Add new PCI ids to support next generation of BladeEngine device. Signed-off-by:
Ajit Khaparde <ajitk@serverengines.com> Signed-off-by:
-
- 15 Oct, 2009 7 commits
-
-
Rémi Denis-Courmont authored
Signed-off-by:
Rémi Denis-Courmont <remi.denis-courmont@nokia.com> Acked-by:
-
Eilon Greenstein authored
Signed-off-by:
Eilon Greenstein <eilong@broadcom.com> Signed-off-by:
-
Eilon Greenstein authored
The device is limited to the maximal BW allocation, so it should be displayed as the link speed to notify the user. Signed-off-by:
-
Eilon Greenstein authored
There is really no need to clear the MAC or the FW filtering rules - it was added for completion, but caused race conditions with load/unload. Removing this redundant code Signed-off-by:
-
Eilon Greenstein authored
DCC commands are not protected with the RTNL lock, so a mutex should be added Signed-off-by:
-
Eilon Greenstein authored
When working with DCC, a function can be disabled or enabled (virtual link down or up). Using the function state introduced some race conditions with the load/unload flow. Using a separate flag to indicate that the function is disabled. Signed-off-by:
-
Eilon Greenstein authored
Signed-off-by:
-
