src/sys/dev/mpt/mpt_debug.c, branch release/9.0.0 FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F9.0.0 2011-07-29T18:35:10Z - Staticize functions as appropriate and comment out unused ones. 2011-07-29T18:35:10Z Marius Strobl marius@FreeBSD.org 2011-07-29T18:35:10Z urn:sha1:87e255ac52df209599578d5af2fb6843afa62a1e - Sprinkle some const where appropriate. - Consistently use target_id_t for the target parameter of mpt_map_physdisk() and mpt_is_raid_volume(). - Fix some whitespace bugs. Approved by: re (kib) Correct spelling. 2011-04-22T09:59:16Z Marius Strobl marius@FreeBSD.org 2011-04-22T09:59:16Z urn:sha1:5ab13afc94ab388a6ef8f7fbe4d757063e411ba4 Submitted by: brucec MFP4: principally to reapply tagged command support to FC and SAS cards. 2006-12-07T22:02:28Z Matt Jacob mjacob@FreeBSD.org 2006-12-07T22:02:28Z urn:sha1:0e0521a153f7aa5ca0366b00feaa450d71480cc7 Fix config page writes to not strip out the attributes when you 2006-07-12T07:48:50Z Matt Jacob mjacob@FreeBSD.org 2006-07-12T07:48:50Z urn:sha1:b4c618c099443efcc9c2d8ffd4eb115009aa4329 actually go write the config page. This fixes the long standing problem about updating NVRAM on Fibre Channel cards and seems so far to not break SPI config page writes. Put back role setting into mpt. That is, you can set a desired role for mpt as a hint. On the next reboot, it'll pick that up and redo the NVRAM settings appropriately and warn you that this won't take effect until the next reboot. This saves people the step of having to find a BIOS utilities disk to set target and/or initiator role for the MPT cards. Add acknowledgements to LSI-Logic for support 2006-05-29T20:34:28Z Matt Jacob mjacob@FreeBSD.org 2006-05-29T20:34:28Z urn:sha1:ec5fe39d397d3df84e39dbf9fe26af55bd011f8d Get most of the way back to having Integrated Mirroring work 2006-05-26T05:54:21Z Matt Jacob mjacob@FreeBSD.org 2006-05-26T05:54:21Z urn:sha1:a3116b5a27afa7be64ad5f7396ecbe4835a3bec9 again- the addition of target mode support broke it massively. Fix some of the previus changes 'better'. 2006-04-01T07:12:18Z Matt Jacob mjacob@FreeBSD.org 2006-04-01T07:12:18Z urn:sha1:5e073106d57b9ef0e2c0e3139fab1843fc82b223 There's something strange going on with async events. They seem to be be treated differently for different Fusion implementations. Some will really tell you when it's okay to free the request that started them. Some won't. Very disconcerting. This is particularily bad when the chip (FC in this case) tells you in the reply that it's not a continuation reply, which means you can free the request that its associated with. However, if you do that, I've found that additional async event replies come back for that message context after you freed it. Very Bad Things Happen. Put in a reply register debounce. Warn about out of range context indices. Use more MPILIB defines where possible. Replace bzero with memset. Add tons more KASSERTS. Do a *lot* more request free list auditting and serial number usages. Get rid of the warning about the short IOC Facts Reply. Go back to 16 bits of context index. Do a lot more target state auditting as well. Make a tag out of not only the ioindex but the request index as well and worry less about keeping a full serial number. Some fairly major changes to this driver. 2006-03-25T07:08:27Z Matt Jacob mjacob@FreeBSD.org 2006-03-25T07:08:27Z urn:sha1:c87e3f833c6b6efcebeeb51abc182c9f3e556071 A) Fibre Channel Target Mode support mostly works (SAS/SPI won't be too far behind). I'd say that this probably works just about as well as isp(4) does right now. Still, it and isp(4) and the whole target mode stack need a bit of tightening. B) The startup sequence has been changed so that after all attaches are done, a set of enable functions are called. The idea here is that the attaches do whatever needs to be done *prior* to a port being enabled and the enables do what need to be done for enabling stuff for a port after it's been enabled. This means that we also have events handled by their proper handlers as we start up. C) Conditional code that means that this driver goes back all the way to RELENG_4 in terms of support. D) Quite a lot of little nitty bug fixes- some discovered by doing RELENG_4 support. We've been living under Giant *waaaayyyyy* too long and it's made some of us (me) sloppy. E) Some shutdown hook stuff that makes sure we don't blow up during a reboot (like by the arrival of a new command from an initiator). There's been some testing and LINT checking, but not as complete as would be liked. Regression testing with Fusion RAID instances has not been possible. Caveat Emptor. Sponsored by: LSI-Logic. Remove the ill-considered effect of using the type definitions as 2006-02-26T22:50:14Z Matt Jacob mjacob@FreeBSD.org 2006-02-26T22:50:14Z urn:sha1:6a9fa0152c730d0cd8d4d04ababe6d660437857c distributed by LSI-Logic. For FreeBSD, just use the posix defines instead of trying to figure out how wide an int is. Apologies to all. Role a microrev of the MPI Library in preparation for target mode work. 2006-02-25T07:45:54Z Matt Jacob mjacob@FreeBSD.org 2006-02-25T07:45:54Z urn:sha1:0b80d21bdfab237033d5553cfabe94cb94215da8 Make my portions of the license clearer. Thank Chris Ellsworth for his support in getting a bunch of this done.