FreeBSD-src - Raptor Engineering's fork of pfsense FreeBSD src with pfSense changes

	Commit message (Collapse)	Author	Age	Files	Lines
*	Convert to use a SYNPOSIS section that mentions kernel modules.	brueffer	2006-05-20	1	-0/+12
\| \| \| \| \| \|	Also add "device scbus" where needed. MFC after: 3 days
*	Update PCI ids to add the E200, E200i, P400, and P400i storage	ps	2005-11-11	1	-1/+7
\| \| \| \| \| \|	controllers. Remove the E400 since it is not a real product. Submitted by: HP
*	Update list of controllers ciss(4) driver	rse	2005-11-03	1	-3/+5
\| \| \| \| \| \| \|	actually supports according to implementation. Submitted by: Christoph Schug <chris@schug.net> MFC after: 1 week
*	Scheduled mdoc(7) sweep.	ru	2005-01-12	1	-1/+0
\|
*	- Add a HARDWARE section which lists supported devices.	simon	2004-08-03	1	-3/+6
\|
*	Mechanically kill hard sentence breaks and double whitespaces.	ru	2004-07-03	1	-4/+7
\|
*	Document the new passthrough interface.	scottl	2004-06-23	1	-1/+10
\|
*	Add HP Smart Array 6422 and V100 to the list of supported controllers.	simon	2004-06-14	1	-0/+4
\|
*	Add support for the HP Modular Smart Array 20 & 500 storage arrays.	ps	2004-04-16	1	-0/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Logical volumes on these devices show up as LUNs behind another controller (also known as proxy controller). In order to issue firmware commands for a volume on a proxy controller, they must be targeted at the address of the proxy controller it is attached to, not the Host/PCI controller. A proxy controller is defined as a device listed in the INQUIRY PHYSICAL LUNS command who's L2 and L3 SCSI addresses are zero. The corresponding address returned defines which "bus" the controller lives on and we use this to create a virtual CAM bus. A logical volume's addresses first byte defines the logical drive number. The second byte defines the bus that it is attached to which corresponds to the BUS of the proxy controller's found or the Host/PCI controller. Change event notification to be handled in its own kernel thread. This is needed since some events may require the driver to sleep on some operations and this cannot be done during interrupt context. With this change, it is now possible to create and destroy logical volumes from FreeBSD, but it requires a native application to construct the proper firmware commands which is not publicly available. Special thanks to John Cagle @ HP for providing remote access to all the hardware and beating on the storage engineers at HP to answer my questions.
*	Synchronize the list of support devices with the driver source code.	simon	2003-11-07	1	-0/+12
\|
*	mdoc(7) police: Scheduled sweep.	ru	2003-02-24	1	-26/+31
\|
*	Add a COMPATIBILITY section. Note what is not supported.	trhodes	2002-12-31	1	-1/+4
\| \| \| \|	Prompted by: olgeni
*	s/arn't/are not/	trhodes	2002-12-31	1	-4/+3
\| \| \| \|	Reword the AUTHORS section to make more sense.
*	Actually cvs add the ciss.4 file...	trhodes	2002-12-30	1	-0/+86