linux

History

Dan Carpenter 82e6bb0398 Staging: silicom: use kstrtoint_from_user() The main problem with the hand rolled code was that there weren't any range checks so you could corrupt memory by writing too much data to the proc file. Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Daniel Cotey <puff65537@bansheeslibrary.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2012-09-17 05:22:09 -07:00
..
bypasslib	Staging: silicom: minor cleanup: remove unused define	2012-09-11 14:31:52 -07:00
bits.h
bp_ioctl.h	Staging: silicom: minor cleanup: remove unused define	2012-09-11 14:31:52 -07:00
bp_mod.c	Staging: silicom: use kstrtoint_from_user()	2012-09-17 05:22:09 -07:00
bp_mod.h	Staging: silicom: checkpatch cleanup: header tabs n spaces	2012-09-11 14:31:52 -07:00
bp_proc.c	Staging: silicom: remove S_IWOTH from proc declaration	2012-09-12 09:43:45 -07:00
bypass.h	Staging: silicom: C99 cleanup of bypass.h	2012-09-07 22:15:10 -07:00
Kconfig	Staging: silicom: Force depend on module	2012-09-10 11:19:34 -07:00
libbp_sd.h	Staging: silicom: Header-cleanup	2012-09-10 15:45:27 -07:00
Makefile
README
TODO	Staging: silicom: Force depend on module	2012-09-10 11:19:34 -07:00

README

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.