summaryrefslogtreecommitdiffstats
path: root/sys/dev/tws/tws.c
Commit message (Collapse)AuthorAgeFilesLines
* MFC r272000:smh2014-12-211-2/+12
| | | | | | Switch from timeout(9) to callout(9) Sponsored by: Multiplay
* Re-do r255853. Along with adding back the API/ABI changes from thescottl2013-09-251-0/+1
| | | | | | | | original, this hides the contents of cam_compat.h from ktrace/kdump/truss, avoiding problems there. There are no user-servicable parts in there, so no need for those tools to be groping around in there. Approved by: re
* Revert r255853 pending fixes to build errors in usr.bin/kdumpgjb2013-09-251-1/+0
| | | | Approved by: re (implicit)
* Update the CAM API for FreeBSD 10:scottl2013-09-241-0/+1
| | | | | | | | | | | | | | | | | | | | | | - Remove the timeout_ch field. It's been deprecated since FreeBSD 7.0; MPSAFE drivers should be managing their own timeout storage. The remaining non-MPSAFE drivers have been modified to also manage their own storage, and should be considered for updating to MPSAFE (or removal) during the FreeBSD 10.x lifecycle. - Add fields related to soft timeouts and quality of service, to be used in upcoming work. - Add room for more flags in the CCB header and path_inq structures. - Begin support for extended 64-bit LUNs. - Bump the CAM version number to 0x18, but add compat shims. Tested with camcontrol and smartctl. Reviewed by: nathanw, ken, kib Approved by: re Obtained from: Netflix
* Update PCI drivers to no longer look at the MEMIO-enabled bit in the PCIscottl2013-08-121-15/+2
| | | | | | | | | | | | | | | | | command register. The lazy BAR allocation code in FreeBSD sometimes disables this bit when it detects a range conflict, and will re-enable it on demand when a driver allocates the BAR. Thus, the bit is no longer a reliable indication of capability, and should not be checked. This results in the elimination of a lot of code from drivers, and also gives the opportunity to simplify a lot of drivers to use a helper API to set the busmaster enable bit. This changes fixes some recent reports of disk controllers and their associated drives/enclosures disappearing during boot. Submitted by: jhb Reviewed by: jfv, marius, achadd, achim MFC after: 1 day
* Integrate changes from LSI vendor driver 10.80.00.005 to FreeBSD.delphij2012-10-191-0/+7
| | | | | | PR: kern/172833 Submitted by: "Charles O'Donnell" <cao bus net> MFC after: 1 week
* Specify MTX_RECURSE for the controller's io_lock. Without it, tws(4)jimharris2012-09-241-1/+1
| | | | | | | | | immediately panics on boot with INVARIANTS enabled. The driver already clearly expects to be able to recurse on this mutex - the main I/O is always recursing on this lock. Reported and tested by: Mike Tancsa <mike at sentex dot net> MFC after: 1 week
* Convert a number of drivers to obtaining their parent DMA tag from theirscottl2012-03-121-1/+1
| | | | PCI device attachment.
* Match surrounding style.delphij2012-01-161-1/+1
| | | | Noticed by: avg
* Don't forget to release queue lock when allocation of memory failed.delphij2012-01-031-0/+1
| | | | | | Submitted by: Sascha Wildner <saw online de> Obtained from: DragonFly MFC after: 2 weeks
* - There's no need to overwrite the default device method with the defaultmarius2011-11-221-6/+4
| | | | | | | | | | one. Interestingly, these are actually the default for quite some time (bus_generic_driver_added(9) since r52045 and bus_generic_print_child(9) since r52045) but even recently added device drivers do this unnecessarily. Discussed with: jhb, marcel - While at it, use DEVMETHOD_END. Discussed with: jhb - Also while at it, use __FBSDID.
* Return BUS_PROBE_DEFAULT instead of 0 (BUS_PROBE_SPECIFIC), allowingdelphij2011-10-171-1/+1
| | | | | | vendor provided driver to override in kernel driver. MFC after: 3 days
* Add the 9750 SATA+SAS 6Gb/s RAID controller card driver, tws(4). Manydelphij2011-10-041-0/+905
thanks for their contiued support to FreeBSD. This is version 10.80.00.003 from codeset 10.2.1 [1] Obtained from: LSI http://kb.lsi.com/Download16574.aspx [1]
OpenPOWER on IntegriCloud