summaryrefslogtreecommitdiffstats
path: root/sys/dev/iir/iir.c
Commit message (Collapse)AuthorAgeFilesLines
* Update email addresses, copyrights, and tweak the management interface.scottl2003-09-261-5/+9
| | | | Submitted by: "Leubner, Achim" <Achim_Leubner@adaptec.com>
* Use __FBSDID().obrien2003-08-241-1/+2
| | | | Also some minor style cleanups.
* Mega busdma API commit.scottl2003-07-011-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | Add two new arguments to bus_dma_tag_create(): lockfunc and lockfuncarg. Lockfunc allows a driver to provide a function for managing its locking semantics while using busdma. At the moment, this is used for the asynchronous busdma_swi and callback mechanism. Two lockfunc implementations are provided: busdma_lock_mutex() performs standard mutex operations on the mutex that is specified from lockfuncarg. dftl_lock() is a panic implementation and is defaulted to when NULL, NULL are passed to bus_dma_tag_create(). The only time that NULL, NULL should ever be used is when the driver ensures that bus_dmamap_load() will not be deferred. Drivers that do not provide their own locking can pass busdma_lock_mutex,&Giant args in order to preserve the former behaviour. sparc64 and powerpc do not provide real busdma_swi functions, so this is largely a noop on those platforms. The busdma_swi on is64 is not properly locked yet, so warnings will be emitted on this platform when busdma callback deferrals happen. If anyone gets panics or warnings from dflt_lock() being called, please let me know right away. Reviewed by: tmm, gibbs
* Import latest changes from the vendor. This also is reported to fix thescottl2003-04-251-25/+38
| | | | | | | driver at long last! Many thanks to vaidas.damosevicius@if.lt for keeping this issue alive and pursuing Intel for a fix, Intel/ICP for working on the driver, and Sergey Osokin for bringing the original patches up to 5-CURRENT.
* I deserve a big pointy hat for having missed all those referencesmux2003-04-101-2/+2
| | | | to bus_dmasync_op_t in my last commit.
* Be consistent about "static" functions: if the function is markedphk2002-09-281-2/+2
| | | | | | static in its prototype, mark it static at the definition too. Inspired by: FlexeLint warning #512
* Don't include <stddef.h> "For offsetof". This is not even wrong inbde2002-05-131-2/+0
| | | | | | | | | -current, since offsetof() is defined a header under /sys so that system sources don't need to have this wrong include. This bug was only detected because my version of <stddef.h> has some spelling fixes (s/field/member/g) and gcc is now sensitive to the spelling of arg names in macros as required by standards (ISO C90 6.8.3...).
* Move the new byte order function prototypes from <sys/param.h> tomike2002-04-261-0/+1
| | | | <sys/endian.h>. This puts us in line with NetBSD and OpenBSD.
* Add the 'iir' driver, for the Intel Integrated RAID controllers andmsmith2002-01-201-0/+2018
prior ICP Vortex models. This driver was developed by Achim Leubner of Intel (previously with ICP Vortex) and Boji Kannanthanam of Intel. Submitted by: "Kannanthanam, Boji T" <boji.t.kannanthanam@intel.com> MFC after: 2 weeks
OpenPOWER on IntegriCloud