From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Shimrit Malichi <smalichi@codeaurora.org>,
Tatyana Brokhman <tlinder@codeaurora.org>,
USB list <linux-usb@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>,
target-devel@vger.kernel.org
Subject: Re: [RFC] UASP on target
Date: Mon, 05 Dec 2011 17:52:31 +0100 [thread overview]
Message-ID: <4EDCF6CF.6020902@linutronix.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1112051109040.5138-100000@iolanthe.rowland.org>
On 12/05/2011 05:10 PM, Alan Stern wrote:
> Evidently you were able to find enough information about the target
> framework to write a driver using it. Can you tell us where this
> information is? It hasn't been easy to locate.
Hehe. Well, I've been told that the target framework has everything one
needs to get it done so I've been digging in the code. First I tried to
come up with an easy setup where I can use it. _This_ was already hard
to get done for someone who is not familiar with scsi. Once I had all
pieces together I wrote this [0].With this information I know more or
less how that thing works or should work.
So at this point I understood that I need to comeup with somethin like
tcm_loop or tcm_vhost. Looking at the host side of the uas driver it is
using SAS as the protocol and nothing special if you ignore "struct iu"
for a moment.
Then I found the python script in Documentation/target which creates you
a skeleton driver. So I used this and started hacking. First I took
the usb descriptors and looked what happens after I connected the
dummy_hcd driver/gadget. I received a usb command message. So now I try
to wire it up in target. I look at the loopback/vhost_scsi for some
inspiration. Other than that I have no additional information....
[0] http://article.gmane.org/gmane.linux.scsi.target.devel/654
> Alan Stern
Sebastian
next prev parent reply other threads:[~2011-12-05 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 19:53 [RFC/PATCH v4 1/3] uas: MS UAS Gadget driver - Infrastructure Shimrit Malichi
2011-12-05 8:20 ` [RFC] UASP on target (was: [RFC/PATCH v4 1/3] uas: MS UAS Gadget driver - Infrastructure) Sebastian Andrzej Siewior
2011-12-05 8:23 ` Sebastian Andrzej Siewior
2011-12-05 8:39 ` Felipe Balbi
2011-12-05 8:55 ` [RFC] UASP on target Sebastian Andrzej Siewior
2011-12-05 9:11 ` Felipe Balbi
2011-12-05 12:10 ` Shimrit Malichi
2011-12-05 12:14 ` Felipe Balbi
2011-12-05 16:10 ` [RFC] UASP on target (was: [RFC/PATCH v4 1/3] uas: MS UAS Gadget driver - Infrastructure) Alan Stern
2011-12-05 16:52 ` Sebastian Andrzej Siewior [this message]
2011-12-06 7:40 ` Nicholas A. Bellinger
2011-12-06 9:19 ` [RFC] UASP on target Sebastian Andrzej Siewior
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=4EDCF6CF.6020902@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=smalichi@codeaurora.org \
--cc=stern@rowland.harvard.edu \
--cc=target-devel@vger.kernel.org \
--cc=tlinder@codeaurora.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