From: grundler@dsl2.external.hp.com (Grant Grundler)
To: "Buechler, Mark R" <Mark_R_Buechler@bausch.com>
Cc: "'parisc-linux@lists.parisc-linux.org'"
<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] A3308 fibre SCSI bridge support
Date: Mon, 30 Dec 2002 12:43:50 -0700 [thread overview]
Message-ID: <20021230194350.GE20066@dsl2.external.hp.com> (raw)
In-Reply-To: <B0E6075E55C7D6119DDE0002A53F8BCE0DE458@blmsrocopc07.bausch.com>
On Mon, Dec 30, 2002 at 10:13:24AM -0500, Buechler, Mark R wrote:
> Configuring the MUX isn't a problem.
ok.
> What I'd like to do is access the SCSI
> devices connected to the MUX from Linux. From a Linux host I see the MUX as
> a single target.
Can you copy the output here?
I'm curious how it's reported.
> I wouldn't think any changes would be necessary for the FC
> driver but rather a separate driver would exist that scans for the MUX and
> uses the Linux sg driver to communicate with it.
the sg driver is a passthru interface and doesn't present a "random
access mass storage device" view. sg would be used to configure
the MUX and sd to access the devices behind it.
My point was the existing FC interface drivers already present FC
storage devices (eg disks or arrays) via "sd" driver and don't know how
to talk to devices that aren't "transperent" (ie invisible nodes in the
FC fabric).
next prev parent reply other threads:[~2002-12-30 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 15:13 [parisc-linux] A3308 fibre SCSI bridge support Buechler, Mark R
2002-12-30 19:43 ` Grant Grundler [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-30 19:54 Buechler, Mark R
2002-12-29 21:02 Mark R. Buechler
2002-12-30 6:45 ` Grant Grundler
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=20021230194350.GE20066@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=Mark_R_Buechler@bausch.com \
--cc=parisc-linux@lists.parisc-linux.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