From: Douglas Gilbert <dougg@torque.net>
To: Linux Bigot <linuxopinion@yahoo.com>, linux-kernel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: SCSI driver query
Date: Sun, 14 Oct 2001 00:51:42 -0400 [thread overview]
Message-ID: <3BC919DE.7E3C9F23@torque.net> (raw)
Linux Bigot <linuxopinion@yahoo.com> wrote:
> How is the ioctl() entry point in Scsi_Host_Template
> used. What device node is associated with it and what
> all commands can be passed down through this
> interface.
That ioctl can be accessed (if defined) via a "trickle
down" ioctl call to any open SCSI device name (e.g. /dev/sda).
When an ioctl is called on an open SCSI device name
then the first match in the following list processes
it:
- the associated upper level SCSI driver looks for
a match on the ioctl 'cmd' number
- the mid-level looks for a match on the ioctl
'cmd' number
- otherwise if Scsi_Host_Template::ioctl is non-NULL
then it is called for the given SCSI device with
the 'cmd' and 'arg' of the original user ioctl call
A SCSI lower level (adapter) driver is not required to
support Scsi_Host_Template::ioctl in which case it will
be NULL. If it is supported then it is up to that adapter
driver what is supported.
This mechanism only allows an adapter which has attached
SCSI devices to be sent an ioctl. The proc_fs interface
may be useful for contacting an adapter driver even if it
doesn't have any attached devices. Something like:
$ echo "<some_command>" > /proc/scsi/advansys/0
Doug Gilbert
next reply other threads:[~2001-10-14 4:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-14 4:51 Douglas Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-12 19:36 SCSI driver query Linux Bigot
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=3BC919DE.7E3C9F23@torque.net \
--to=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxopinion@yahoo.com \
/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