From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 30 May 1997 08:45:12 +0100 From: Nigel Roles ngr@symbionics.co.uk Subject: Adaptec 2940 (buy NCR/Symbios) [long] Topicbox-Message-UUID: 5b7735c2-eac8-11e9-9e20-41e7f4b1d025 Message-ID: <19970530074512.ElMN_5MqBuIzoOtfq0B09gCKMsuC8L5VoDs9JjFk8sI@z> Before I talk about the Adaptec AIC7xxx series, I would like to back up forsyth's kind comments about the Symbios/NCR driver. If you don't have an explicit need for an Adaptec controller, then the Symbios/NCR route is cheaper, and higher performance. The Symbios 8751 Ultra Wide controller now costs 110 quid here, whilst Adaptec is pushing 200 quid for equivalents. I can't make comparisons under Plan 9, but under NT commerical projects here have found 30% throughput, and better reliability by switching to Symbios cards. So why would I want to do an Adaptec driver? It's all Uncle Bill's fault. Under Win95, the only well documented generic SCSI layer is the ASPI layer which was invented by Adaptec (though they claim the A stands for Advanced). It is possible to use the miniport layer (and hence drive any controller) but few applications do (Seagate Backup for WIn95 is an example) and the documentation seems to be designed to convince you that it only works under NT so it's difficult to believe any part of it. As a result, anyone writing software for SCSI will support one proprietary controller directly, and then ASPI. This is the case with TWAIN drivers for scanners. Since scanners tend to have manufacturer specific extensions, each model has it's own TWAIN driver to do the twiddly bits. These drivers talk to either the crappy card shipped with the scanner, or ASPI. In my case, the card the scanner's shipped with is so bad there's no motivation to write a driver for it. So I need an ASPI driver for NCR/Symbios. Ha! This is what Symbios say: Q: I need an ASPI driver to function devices outside of the hard drive? A: We do not provide the ASPI driver under Windows 95. If the driver does not come with the device then your only solution is to go with another Host Adapter thats provides an ASPI driver under Windows 95. This is clearly a ridiculous statement because ASPI is a driver for a controller, not a peripheral. Anyhow, at least I know where I stand. So, if I want to drive the scanner under Plan 9 and Win 95, I could either 1) write an ASPI driver for Symbios under Win 95 2) write an Adaptec AIC7xxx driver under Plan 9 3) use the Adaptec 1542 which is in my fileserver Which would be less painful? Well 3, but 1 is out of the question. So, on to Adaptec.... I've been in touch with the Linux/FreeBSD guys who were great. I have a full reading list for Adaptec. You think you only need one manual. It looked like about 10. The AIC chip runs microcode much like the NCR, except that there is an on-board copy which can be replaced by download. Apparently, Adaptec will not document the microcode except under NDA, so Linux/FreeBSD has it's own. The microcode sequencer is better than NCRs (it avoids several big mistakes). The microcode reproduces the control block concept that is used by the unreplaceable (should that be irreplaceable) 8085 machine code on the 1540 ISA cards. This suggests to me that we could borrow the FreeBSD sequencer, and 'adapt' (ha ha ha) the existing Plan9 aha154x driver. There's the usual load of crud to identify the card, download code, read and write a microwire EEPROM, patch up for the fact that some wide controllers actually are two AIC controllers bolted together, etc etc Nigel Roles, Symbionics