From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Andy Grover <agrover@redhat.com>
Cc: linux-scsi@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
target-devel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net
Subject: Re: FireWire/SBP2 Target mode
Date: Wed, 1 Feb 2012 22:41:56 +0100 [thread overview]
Message-ID: <20120201224156.0773ebc6@stein> (raw)
In-Reply-To: <4F29978A.3010707@redhat.com>
On Feb 01 Andy Grover wrote:
> You're saying the sbp2 protocol can theoretically be used other places
> besides firewire? I'd say put it all in the fabric module for now.
While SBP-2 is explicitly specified for IEEE 1394 a.k.a. FireWire only,
it could be used on any bus architecture which implements IEEE 1212
"Control and Status Registers (CSR) Architecture for Microcomputer
Buses". But IEEE 1394 a.k.a. FireWire is nowadays the only remaining IEEE
1212 implementation, as far as I know.
On the other hand, the transport protocol SBP-2 can be used to encapsulate
various protocols besides SCSI. A long time ago I heard that there were
SBP-2 printers that weren't SCSI printers, but I may have confused
something.
The current version of the protocol, SBP-3 which extends SBP-2
in an upwards compatible way, has been developed specifically in
order to transport AV/C command sets. (AV/C is a set of specifications
from the 1394 Trade Association that build on top of IEC 61883 "Consumer
audio/video equipment - Digital interface" and is used for camcorders,
audio interfaces, studio-grade video equipment, TV set top boxes etc.)
But I am not aware of any existing SBP-3 target or SBP-3 initiator which
actually implements AV/C.
So in short,
- SBP-2/3 is only used on the FireWire bus.
- Potentially there could be SBP-2/3 targets or initiators that
implement something else than SCSI. But stock SBP-2/3 initiator
drivers of popular OSs are SCSI initiators, and non-SCSI SBP-2/3
targets are extremely rare or don't exist actually.
--
Stefan Richter
-=====-===-- --=- ----=
http://arcgraph.de/sr/
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
next prev parent reply other threads:[~2012-02-01 21:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 14:51 FireWire/SBP2 Target mode Chris Boot
2011-08-17 18:57 ` Stefan Richter
2011-08-18 16:19 ` Clemens Ladisch
2012-02-01 19:50 ` Andy Grover
2012-02-01 21:41 ` Stefan Richter [this message]
2012-02-02 9:22 ` Boaz Harrosh
2012-02-02 10:09 ` Clemens Ladisch
2012-02-06 13:13 ` Chris Boot
2012-02-06 14:43 ` Clemens Ladisch
2012-02-06 14:51 ` Chris Boot
2012-02-06 20:26 ` Stefan Richter
2012-02-06 22:28 ` Chris Boot
2012-02-06 23:00 ` Julian Calaby
2012-02-06 23:09 ` Chris Boot
2012-02-07 7:38 ` Chris Boot
2012-02-07 10:06 ` Julian Calaby
2012-02-07 19:17 ` Stefan Richter
2012-02-07 19:53 ` Chris Boot
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=20120201224156.0773ebc6@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=agrover@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=target-devel@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;
as well as URLs for NNTP newsgroup(s).