src-test2/sys/dev/aac/aacvar.h, branch release/6.2.0_cvs FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F6.2.0_cvs 2007-01-11T22:54:46Z This commit was manufactured by cvs2svn to create tag 2007-01-11T22:54:46Z cvs2svn cvs2svn@FreeBSD.org 2007-01-11T22:54:46Z urn:sha1:201f78d6b90635d961fa373ecd706e3786333b7e 'RELENG_6_2_0_RELEASE'. This commit was manufactured to restore the state of the 6.2-RELEASE image. MFC: Support new adapters and new communication protocol. 2005-10-09T06:39:21Z Scott Long scottl@FreeBSD.org 2005-10-09T06:39:21Z urn:sha1:727e45252f1694f68283b29f572eec8222c2b539 Submitted by: Adaptec, Inc. Approved by: re Add support for the Adaptec RAID-On-Chip architecture. This in turn 2004-08-13T01:44:09Z Scott Long scottl@FreeBSD.org 2004-08-13T01:44:09Z urn:sha1:4afedc314e8e6ded5fb719708bcc78deba2eadcb provides support for the Adaptec 2130S adapter. Thanks to Adaptec for providing hardware for this. Remove the AAC_LOCK macros. They no longer abstract anything and only 2004-08-12T05:05:06Z Scott Long scottl@FreeBSD.org 2004-08-12T05:05:06Z urn:sha1:bb6fe253cc602e4a0a4ba3a96b9d1da80f3c4e56 obfuscate the code. No functional differences. Do the dreaded s/dev_t/struct cdev */ 2004-06-16T09:47:26Z Poul-Henning Kamp phk@FreeBSD.org 2004-06-16T09:47:26Z urn:sha1:89c9c53da05197f657dfe8e0bdda6941a2e9a0d4 Bump __FreeBSD_version accordingly. Collapse sync fib locking into normal i/o locking. The former didn't 2004-06-02T18:15:48Z Scott Long scottl@FreeBSD.org 2004-06-02T18:15:48Z urn:sha1:03b5fe51bfd6cb2d7987a4e9504cb9fdb0636558 protect the registers so it was trivially possible for a sync command and i/o command to fight each other and confuse the controller. Make the sync fib alloc/release functions inline and remove the somewhat worthless AAC_SYNC_LOCK_FORCE flag. Thanks to Adil Katchi for helping me to track this down in RELENG_4. Turn down the queue size by 8 until I can figure out why the 512th command 2004-05-30T22:40:28Z Scott Long scottl@FreeBSD.org 2004-05-30T22:40:28Z urn:sha1:2c81db6cb5589a7fb41e3f35e196a427fc4b7a0c keeps on getting lost. Change the disk(9) API in order to make device removal more robust. 2004-02-18T21:36:53Z Poul-Henning Kamp phk@FreeBSD.org 2004-02-18T21:36:53Z urn:sha1:0b7ed341e106c1583e873116529015d2ae042fd0 Previously the "struct disk" were owned by the device driver and this gave us problems when the device disappared and the users of that device were not immediately disappearing. Now the struct disk is allocate with a new call, disk_alloc() and owned by geom_disk and just abandonned by the device driver when disk_create() is called. Unfortunately, this results in a ton of "s/\./->/" changes to device drivers. Since I'm doing the sweep anyway, a couple of other API improvements have been carried out at the same time: The Giant awareness flag has been flipped from DISKFLAG_NOGIANT to DISKFLAG_NEEDSGIANT A version number have been added to disk_create() so that we can detect, report and ignore binary drivers with old ABI in the future. Manual page update to follow shortly. Do some small cleanups to comments and remove AACQ_COMPLETE definitions since 2004-02-07T17:40:38Z Scott Long scottl@FreeBSD.org 2004-02-07T17:40:38Z urn:sha1:ecd1c51f920dc6c90201a217a70519166eb5f89f the completion queue is long-gone. Remove the hack of lowering AAC_MAX_FIB now that the root cause of the 2004-02-07T10:30:59Z Scott Long scottl@FreeBSD.org 2004-02-07T10:30:59Z urn:sha1:d85f27ce7fc1a9c4a739c4c923355e113d6513d9 problem was found.