#
dd83a01e |
| 30-May-2004 |
Scott Long <scottl@FreeBSD.org> |
Use a unique malloc type rather than M_DEVBUF.
|
Revision tags: release/4.10.0_cvs, release/4.10.0 |
|
#
b234a120 |
| 28-Feb-2004 |
Scott Long <scottl@FreeBSD.org> |
Switch from using mutexes to using semaphores to protect against early completion of synchronous commands. Also switch to a per-array bioq as it appears to improve performance.
Submitted by: mbr, i
Switch from using mutexes to using semaphores to protect against early completion of synchronous commands. Also switch to a per-array bioq as it appears to improve performance.
Submitted by: mbr, imp.ch (bioq change)
show more ...
|
Revision tags: release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0 |
|
#
aa8689ef |
| 01-Jan-2004 |
Martin Blapp <mbr@FreeBSD.org> |
The reset_type should not be 0x80, it should be set to zero. 0x80 can cause the command to be rejected as invalid. This bug exists also in the Linux IPS ffdc code.
Submitted by: David Jeffery MFC af
The reset_type should not be 0x80, it should be set to zero. 0x80 can cause the command to be rejected as invalid. This bug exists also in the Linux IPS ffdc code.
Submitted by: David Jeffery MFC after: 1 week
show more ...
|
#
7633e7f1 |
| 27-Nov-2003 |
Martin Blapp <mbr@FreeBSD.org> |
ServeRaid (at least 5i) didn't initialize correctly. To get them working (cache, automatic rebuild and hotswap) the FFDC info (First Failure Data Capture) on the adapter must be initialised.
Logical
ServeRaid (at least 5i) didn't initialize correctly. To get them working (cache, automatic rebuild and hotswap) the FFDC info (First Failure Data Capture) on the adapter must be initialised.
Logical drives in critical/degraded states weren't added to the drive list. FreeBSD was not able to see a degraded array after a reboot. Degraded drives are now also added to the drivelist and the state of the logical drive is given at boottime.
The adapter type is detected from informations in nvram page 5 and displayed at boottime.
Change IPS_OS_FREEBSD definition from 10 to 8 according to IBM specs.
Submitted by: <Patrick Guelat> pgfb@imp.ch Reviewed by: mbr, scottl Approved by: re
show more ...
|
Revision tags: release/4.9.0_cvs, release/4.9.0 |
|
#
0eac610f |
| 18-Oct-2003 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Eliminate reporting of bio_blkno.
|
#
aad970f1 |
| 24-Aug-2003 |
David E. O'Brien <obrien@FreeBSD.org> |
Use __FBSDID(). Also some minor style cleanups.
|
#
f6b1c44d |
| 01-Jul-2003 |
Scott Long <scottl@FreeBSD.org> |
Mega busdma API commit.
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.
Mega busdma API commit.
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
show more ...
|
#
f472527c |
| 28-Jun-2003 |
Peter Wemm <peter@FreeBSD.org> |
Fix pointer/int warnings so this compiles on amd64. The driver wants to store an int in the bio->bio_driver1 (a void *). It is big enough, but you have to match the int sizes first before doing the
Fix pointer/int warnings so this compiles on amd64. The driver wants to store an int in the bio->bio_driver1 (a void *). It is big enough, but you have to match the int sizes first before doing the cast.
Glanced at by: scottl
show more ...
|
#
dea4622d |
| 26-Jun-2003 |
Scott Long <scottl@FreeBSD.org> |
- Zero the buffers used to hold configuration data from the card. Not doing so can leave stale data in the buffer and confuse the driver. - enable the ability to set the 'disable' hint for the dri
- Zero the buffers used to hold configuration data from the card. Not doing so can leave stale data in the buffer and confuse the driver. - enable the ability to set the 'disable' hint for the driver to keep it from attaching. i.e. 'hw.ips.0.disable=1' will prevent the driver from attaching. - Only detach if attach suceeded.
Submitted by: mjacob
show more ...
|
Revision tags: release/5.1.0_cvs, release/5.1.0 |
|
#
2aedd662 |
| 11-May-2003 |
Scott Long <scottl@FreeBSD.org> |
Add the 'ips' driver for the IBM (now Adaptec) ServeRAID controller series. This driver was generously developed and released by David Jeffreys and Adaptec. I've updated it to work with 5.x and fix
Add the 'ips' driver for the IBM (now Adaptec) ServeRAID controller series. This driver was generously developed and released by David Jeffreys and Adaptec. I've updated it to work with 5.x and fixed a few bugs.
MFC After: 1 week
show more ...
|