linux

History

Ben Hutchings a1606c7dc6 net: Move MII out from under NET_CORE and hide it All drivers that select MII also need to select NET_CORE because MII depends on it. This is a bit ridiculous because NET_CORE is just a menu option that doesn't enable any code by itself. There is also no need for it to be a visible option, since its users all select it. Signed-off-by: Ben Hutchings <ben@decadent.org.uk> Acked-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2013-06-19 22:22:56 -07:00
..
bypasslib	staging: fix all sparse warnings in silicom/bypasslib/	2013-03-11 09:43:40 -07: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: bp_mod.h: checkpatch tab and space cleanup	2012-09-17 05:37:56 -07:00
bpctl_mod.c	net: pass info struct via netdevice notifier	2013-05-28 13:11:01 -07:00
bypass.h	Staging: silicom: bypass.h: checkpatch whitespace	2012-09-17 05:37:57 -07:00
Kconfig	net: Move MII out from under NET_CORE and hide it	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

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.