From: Herbert Poetzl <herbert@13thfloor.at>
To: James Bottomley <James.Bottomley@suse.de>
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, 3 Apr 2011 19:39:03 +0200 [thread overview]
Message-ID: <20110403173903.GK25397@MAIL.13thfloor.at> (raw)
In-Reply-To: <1295964854.4955.21.camel@mulgrave.site>
On Tue, Jan 25, 2011 at 09:14:14AM -0500, James Bottomley wrote:
> On Tue, 2011-01-25 at 04:07 +0100, Herbert Poetzl wrote:
>> On Mon, Jan 17, 2011 at 06:24:15PM +0100, Tejun Heo wrote:
>>> On Mon, Jan 17, 2011 at 11:21:46AM -0600, James Bottomley wrote:
>>>> Expanders aren't SCSI devices either ... that means they don't
>>>> appear as visible to standard SCSI mechanisms like INQUIRY (SMP
>>>> isn't a SCSI protocol it's a SAS extension). They just appear as
>>>> part of the topology in the device tree.
>>> Ah, okay. Then, things would be much simpler. I was worrying about
>>> how it would map to SCSI layer including INQUIRY emulations and all
>>> those stuff. Thanks for the info.
>> 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?
> That would allow the ses ULD to attach seamlessly.
any pointers to such an SES ULD (maybe for testing)?
thanks in advance,
Herbert
> James
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-04-03 17:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110113192558.GE16039@MAIL.13thfloor.at>
[not found] ` <20110114142018.GA978@htj.dyndns.org>
[not found] ` <20110114165957.GH16039@MAIL.13thfloor.at>
[not found] ` <20110114170407.GE978@htj.dyndns.org>
[not found] ` <20110114173759.GI16039@MAIL.13thfloor.at>
2011-01-17 15:40 ` PMP and SEMB messages to SEP 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 [this message]
2011-04-03 18:38 ` James Bottomley
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=20110403173903.GK25397@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=James.Bottomley@suse.de \
--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