From: Markus Lidel <Markus.Lidel@shadowconnect.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Arjan van de Ven <arjanv@redhat.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: I2O enhancement for Adaptec management software
Date: Fri, 23 Apr 2004 10:31:45 +0200 [thread overview]
Message-ID: <4088D471.9000201@shadowconnect.com> (raw)
In-Reply-To: <1081427380.1885.4.camel@mulgrave>
Hello,
James Bottomley wrote:
>>The patch is for i2o_config, not for dpt_i2o! These are different
>>drivers and have (from the architecture view) not much in common.
>>dpt_i2o is a driver which let access to the disks entirely using the
>>SCSI subsystem. The i2o subsystem uses i2o_core and i2o_block to access
>>disks (which doesn't use SCSI at all), and also have an SCSI driver,
>>which let access to each connected disk (i2o_scsi). But the i2o_scsi is
>>not needed for normal disk access.
> There appears to be some confusion: SG_IO is a *block* layer ioctl (it
> happens to be in the slightly misnamed drivers/block/scsi_ioctl.c file,
> but it is usable for all block devices).
As promised i have looked at the sg_io() function, but i think it's not
possible to use this function, because it is for block devices, but the
i2o_config uses a char device to communicate with the controller. I
didn't find a function, which makes the same as sg_io, but only with
char devices.
Any suggestions, what to do in this case?
Best regards,
Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)
Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany
Phone: +49 82 82/99 51-0
Fax: +49 82 82/99 51-11
E-Mail: Markus.Lidel@shadowconnect.com
URL: http://www.shadowconnect.com
next prev parent reply other threads:[~2004-04-23 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 9:43 I2O enhancement for Adaptec management software Markus Lidel
2004-04-05 10:02 ` Arjan van de Ven
2004-04-05 10:05 ` Christoph Hellwig
2004-04-05 10:10 ` Arjan van de Ven
2004-04-05 10:12 ` Christoph Hellwig
2004-04-07 21:10 ` James Bottomley
2004-04-08 9:27 ` Markus Lidel
2004-04-08 12:29 ` James Bottomley
2004-04-08 13:14 ` Markus Lidel
2004-04-23 8:31 ` Markus Lidel [this message]
2004-04-05 10:18 ` Christoph Hellwig
2004-04-05 10:37 ` Markus Lidel
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=4088D471.9000201@shadowconnect.com \
--to=markus.lidel@shadowconnect.com \
--cc=James.Bottomley@steeleye.com \
--cc=arjanv@redhat.com \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.