From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: target-devel <target-devel@vger.kernel.org>,
linux1394-devel <linux1394-devel@lists.sourceforge.net>,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Chris Boot <bootc@bootc.net>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Clemens Ladisch <clemens@ladisch.de>,
Andy Grover <agrover@redhat.com>
Subject: [GIT PULL] sbp-target merge for v3.5-rc1
Date: Tue, 22 May 2012 15:33:49 -0700 [thread overview]
Message-ID: <1337726029.22481.116.camel@haakon2.linux-iscsi.org> (raw)
Hi Linus,
Here is the next pull request for Chris Boot's new Serial Block Protocol
(sbp) target driver for IEEE-1394 (FireWire) hardware. This code also
has been in linux-next for a number of weeks, and is ready for an
initial merge.
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git sbp-target-merge
The FireWire SBP-2 Target is a driver for using an IEEE-1394 connection
as a SCSI transport. This module uses the SCSI Target framework to
expose LUNs to other machines attached to a FireWire bus, in effect
acting as a FireWire hard disk similar to FireWire Target Disk mode
on many Apple computers.
Also included are the two drivers/firewire/ patches required by
sbp-target to access fw_request fabric speed needed for mgt_agent
TCODE_WRITE_BLOCK_REQUEST ops, and exporting fw_card kref logic used
when creating/destroying active session references to individual
endpoints.
A credit goes to Chris in being able to get this code up and running so
quickly w/o any target core changes, and special thanks goes out to
Stefan Richter + Clemens Ladisch + Andy Grover for their help in getting
this driver ready for mainline. Also, one of Chris's goals was to be
able to connect sbp-target to a PowerPC based MacOS-X based client, that
he accomplished along the way in this obligatory screenshot:
http://linux-iscsi.org/wiki/File:Linux-fireware-target-bootc-macosx.png
Great work Chris + linux-1394 team !!
--nab
Chris Boot (3):
firewire: Add function to get speed from opaque struct fw_request
firewire: Move fw_card kref functions into linux/firewire.h
sbp-target: Initial merge of firewire/ieee-1394 target mode support
MAINTAINERS | 9 +
drivers/firewire/core-card.c | 1 +
drivers/firewire/core-transaction.c | 9 +
drivers/firewire/core.h | 15 -
drivers/target/Kconfig | 1 +
drivers/target/Makefile | 1 +
drivers/target/sbp/Kconfig | 11 +
drivers/target/sbp/Makefile | 1 +
drivers/target/sbp/sbp_target.c | 2621 +++++++++++++++++++++++++++++++++++
drivers/target/sbp/sbp_target.h | 251 ++++
include/linux/firewire.h | 15 +
11 files changed, 2920 insertions(+), 15 deletions(-)
create mode 100644 drivers/target/sbp/Kconfig
create mode 100644 drivers/target/sbp/Makefile
create mode 100644 drivers/target/sbp/sbp_target.c
create mode 100644 drivers/target/sbp/sbp_target.h
next reply other threads:[~2012-05-22 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 22:33 Nicholas A. Bellinger [this message]
2012-05-23 5:01 ` Stefan Richter
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=1337726029.22481.116.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=agrover@redhat.com \
--cc=bootc@bootc.net \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
--cc=target-devel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®