2
0
mirror of https://github.com/edk2-porting/linux-next.git synced 2025-01-06 20:53:54 +08:00
linux-next/drivers/staging/silicom
Michael Hoefler 382d277b38 silicom: remaining checkpatch issues in bypass.c
In this patch we fix some "logical" errors in bypass.c of the silicom bypass
driver (in staging).

Checkpatch complains about the following errors:
 - unnecessary forward declarations in a source file
 - assignment in if condition

In addition to that the __init and __exit macros were missing at the init and
cleanup function.

There are still two warnings left for this file related to too many leadingtabs
at nested blocks. I did not touch this issue becasue the code needs really some
refactoring. And since i do not have the appropriate hardware to test the code,
i do not change the functionality in any way.

Signed-off-by: Michael Hoefler <michael.hoefler@studium.uni-erlangen.de>
Signed-off-by: Christoph Kohl <christoph.kohl@t-online.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-12-20 09:04:49 -08:00
..
bypasslib silicom: remaining checkpatch issues in bypass.c 2013-12-20 09:04:49 -08:00
bits.h
bp_ioctl.h Staging: silicom: minor cleanup: remove unused define 2012-09-11 14:31:52 -07:00
bp_mod.h staging: silicom: fix space prohibited before semicolon 2013-10-02 16:22:01 -07:00
bpctl_mod.c staging: silicom: remove dead code 2013-12-03 09:03:20 -08:00
bypass.h Staging: silicom: bypass.h: checkpatch whitespace 2012-09-17 05:37:57 -07:00
Kconfig net: Add missing dependencies on NETDEVICES 2013-06-19 22:22:56 -07:00
libbp_sd.h Staging: silicom: checkpatch cleanup: header file whitespace 2012-09-17 05:37:57 -07:00
Makefile silicom: bury bp_proc.c 2013-04-09 14:13:13 -04:00
README
TODO Staging: silicom: Force depend on module 2012-09-10 11:19:34 -07:00

Theory of Operation:

The Silicom Bypass Network Interface Cards (NICs) are network cards with paired ports (2 or 4). 
The pairs either act as a "wire" allowing the network packets to pass or insert the device in 
between the two ports.  When paired with the on-board hardware watchdog or other failsafe, 
they provide high availability for the network in the face of software outages or maintenance.

The software requirements are for a kernel level driver that interfaces with the bypass and watchdog,
as well as for control software. User control can be either the provided standalone executable 
(/bin/bpctl) or the API exposed by the Silicom library.