test at Target mode

[Justin T. Gibbs]

>M.Gibbs:
>
>I doubted the hardware, but I cannot prove it.
>It's reassuring that Adaptec co. is backing up.
>When I questioned Adaptec co. on AIC7xxx assembler before,
>they said that the information cannot be opened.
>Now It's pleased to find opened ML and the assembler.

The open sourced code had very little to do with Adaptec.  The
target mode code you are using now was developed and released for
FreeBSD long before I started work at Adaptec.  Most of it was
done with little or now documentation on the chips - just lots
of experimentation.  Adaptec is now supporting the open source
effort (at least the initiator side), but they didn't help
much from 1994-2000 when the bulk of the code was created. 8-)

>Without CAM, target I/O system can be implemented under 6.1.13.
>I have some changes:
>1)When any abort message is received, sequencer should go to BusFree.

This is supposed to be handled by the message handler in the kernel
driver.  Abort is a rare occurance, so, other than honoring ATNI in
all of the right places, the sequencer shouldn't waste instructions on
handling abort on its own.

>2)When any abort message is received, sequencer should set SAVED_LUN.

I believe the original intention was to just upload the "selection packet"
to the host even if no command was sent and pull the info from there.
I don't see much harm in setting the SAVED_LUN field the instruction
after we have verified the identify message.  It will probably assist
in diagnostics.  Making this a special case for the abort path seems
cumbersome.

>3)When ABORT message(=1 bytes message) is received,
>    driver cannot get it because ATNI is off.

You mean the kernel handler for target messages doesn't work for 1
byte messages?  That seems odd.  ATNI should drop after our REQ and
before the ACK for the last byte.  You don't see this hapening?

--
Justin

To Unsubscribe: send mail to majordomo at FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message