home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cbmvax!jesup
- From: jesup@cbmvax.commodore.com (Randell Jesup)
- Newsgroups: comp.periphs.scsi
- Subject: Re: How to reject multiple byte messages
- Message-ID: <38765@cbmvax.commodore.com>
- Date: 25 Jan 93 08:13:46 GMT
- References: <1993Jan15.201455.17389@kpc.com>
- Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
- Organization: Commodore, West Chester, PA
- Lines: 36
-
- jworley@kpc.com (John Worley - Consultant) writes:
- > How does device reject a two byte message, e.g., the tagged
- >queue messages? SCSI-2 doesn't seem to specify and I can see two
- >scenarios:
-
- First, no proper device should send you one if you don't say you
- support it in your Inquiry data. If you do say you support it, you should do
- so.
-
- > (1) The device sends MSG REJECT after the first byte - most
- > devices should do this - after which the sender would
- > need to substitute a NOP message for the 2nd byte, OR
- >
- > (2) The device recognizes the two byte message but doesn't
- > support the operation, accepts both bytes and sends one
- > MSG REJECT.
-
- That's how I would handle it.
-
- > Does an initiator need to support both types of rejection? Please
- >respond by e-mail.
-
- If the initiator checks the inquiry data, it shouldn't need to handle
- either. Note that many many modern drives have broken tagged queuing - I've
- seen one that took the $20 (SIMPLE_QUEUE) and used it for the count of messages
- to fetch, then rejected the whole thing. I've seen another than on request
- sense after using tags will always return BUSY. A bit like Sync negotiations
- in the early SCSI-1 days.
-
- --
- GNU Emacs is a LISP operating system disguised as a word processor.
- - Doug Mohney, in comp.arch
-
- Randell Jesup, Jack-of-quite-a-few-trades, Commodore Engineering.
- jesup@cbmvax.commodore.com BIX: rjesup
- Disclaimer: Nothing I say is anything other than my personal opinion.
-