From: Doug Ledford <dledford@redhat.com>
To: shankar krishna <kshan01@hotmail.com>
Cc: aksumit@india.hp.com, linux-scsi@vger.kernel.org
Subject: Re: building SCSI CDB over FC
Date: Fri, 8 Nov 2002 18:12:44 -0500 [thread overview]
Message-ID: <20021108231244.GI26518@redhat.com> (raw)
In-Reply-To: <F10FGcbNZOBPr0ebmeG00001ecf@hotmail.com>
On Fri, Nov 08, 2002 at 02:03:16PM -0700, shankar krishna wrote:
> Sumit:
> You are correct. I sent the
> following command to send the
> CDB. It did send correctly.
>
> if (ioctl(sd_fd,SCSI_IOCTL_SEND_COMMAND,&cdb_buf))
> {
> /* ERROR */
> }
>
> where cdb_buf is of type Scsi_Ioctl_Command.
>
> DGilbert:
> "
> Notes:
> The SCSI command length is determined by examining the 1st byte of the
> given command [1] . There is no way to override this.
> "
>
> The above claim that 1st octet should be the length
> of CDB is not true...In the analyser I could see
> that "if I sent the length of CDB it is sending
> it as OPCODE" which essentially is the first byte.
>
> You may want to correct it in the
> document(www.torque.net/sg) that you
> told me. It was very useful.
I believe you are mis-interpreting the documentation. The first byte of
the command is the opcode, and with scsi_ioctl_send_command the code reads
the opcode and looks it up in a table to determine the length of the scsi
command, and that length is the length that can't be over-ridden.
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
next prev parent reply other threads:[~2002-11-08 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 21:03 building SCSI CDB over FC shankar krishna
2002-11-08 23:12 ` Doug Ledford [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-08 2:44 shankar krishna
2002-11-08 17:52 ` Sumit Agarwal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021108231244.GI26518@redhat.com \
--to=dledford@redhat.com \
--cc=aksumit@india.hp.com \
--cc=kshan01@hotmail.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox