From: James Bottomley <James.Bottomley@suse.de>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: Tejun Heo <tj@kernel.org>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: PMP and SEMB messages to SEP
Date: Sun, 03 Apr 2011 14:38:22 -0400 [thread overview]
Message-ID: <1301855902.2631.39.camel@mulgrave.site> (raw)
In-Reply-To: <20110403173903.GK25397@MAIL.13thfloor.at>
On Sun, 2011-04-03 at 19:39 +0200, Herbert Poetzl wrote:
> >> So, any thoughts on how and where to add the PMP to the devices
> >> available for sending SCSI or ATA commands to?
>
> >> I'm willing to try to add the required code, but I'm sure I'll
> >> benefit from a few hints from the experts ...
>
> > Well, I'm not sure I'd count as an expert on this piece:
> > I haven't read the relevant ATA standards.
>
> > From what I understand, SES packets are encapsulated over
> > an ATA command for SEMB.
>
> correct, just that it can be any protocol (it's just another
> bus, usually i2c) with the common protocols being SES and
> SAF_TE AFAIK
>
> > In that case, it should be fairly simple to recognise
> > this and present a SCSI device which simply encapsulates
> > everything sent to it over this protocol.
>
> do you have any pointers for me how that is done for SCSI?
I don't think I understand the question. It happens automatically for
anything part of the SCSI domain. For SEMB you have to unwind the
encapsulation and expose the resulting device into the SCSI domain for
the SES ULD to attach, presumably as a libata target or LUN. If you're
asking for basic documentation about how SCSI works, that's in
Documentation/scsi/ plus some of the kernel docbook stuff.
> > That would allow the ses ULD to attach seamlessly.
>
> any pointers to such an SES ULD (maybe for testing)?
it's drivers/scsi/ses.c
James
next prev parent reply other threads:[~2011-04-03 18:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 19:25 PMP and SEMB messages to SEP Herbert Poetzl
2011-01-14 14:20 ` Tejun Heo
2011-01-14 16:59 ` Herbert Poetzl
2011-01-14 17:04 ` Tejun Heo
2011-01-14 17:37 ` Herbert Poetzl
2011-01-17 15:40 ` Tejun Heo
2011-01-17 16:18 ` James Bottomley
2011-01-17 17:13 ` Herbert Poetzl
2011-01-17 17:20 ` Tejun Heo
2011-01-17 17:34 ` Herbert Poetzl
2011-01-17 17:39 ` Tejun Heo
2011-01-17 17:48 ` Herbert Poetzl
2011-01-17 18:05 ` James Bottomley
2011-01-17 18:21 ` Herbert Poetzl
2011-01-17 18:27 ` Herbert Poetzl
2011-01-17 17:18 ` Tejun Heo
2011-01-17 17:21 ` James Bottomley
2011-01-17 17:24 ` Tejun Heo
2011-01-25 3:07 ` Herbert Poetzl
2011-01-25 14:14 ` James Bottomley
2011-04-03 17:39 ` Herbert Poetzl
2011-04-03 18:38 ` James Bottomley [this message]
2011-01-17 18:55 ` Jeff Garzik
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=1301855902.2631.39.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=herbert@13thfloor.at \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tj@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).