From: Tejun Heo <tj@kernel.org>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: James Bottomley <James.Bottomley@suse.de>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: PMP and SEMB messages to SEP
Date: Mon, 17 Jan 2011 18:39:46 +0100 [thread overview]
Message-ID: <20110117173946.GL27123@htj.dyndns.org> (raw)
In-Reply-To: <20110117173433.GM16039@MAIL.13thfloor.at>
On Mon, Jan 17, 2011 at 06:34:33PM +0100, Herbert Poetzl wrote:
> hmm, haven't had the time to dig through the specs yet, but
> at least addonics seems to disagree here:
>
> http://www.addonics.com/products/host_controller/tutorial_pm.asp
>
> but maybe that's just a marketing page with no relation
> to reality ....
That's hardware RAID PMP. It would just show up as a single drive to
the host. They can do whatever they want to if they do that.
> > AFAIK, it just doesn't care. It could be ses-2 or whatever else. It
> > just transmits the binary blob it receives via sysfs and vice-versa.
>
> the interesting part here is, that the AHCI host controller
> my PMP is connected to recognizes the PMP perfectly fine
> (i.e. more than one drive works just as expected), but doesn't
> seem to allow for the em_message part (despite the fact that
> the attached PMP seems to be SEMB/SEP capable) ...
>
> maybe this is just a bug in the kernel code, maybe the AHCI
> implementation doesn't allow a PMP to receive enclosure
> management messages at all ...
AFAIK, the ahci em message thing is not via PMP. It's for cases where
the ahci controller is directly connected to an enclosure. Well,
that's my understanding anyway.
--
tejun
next prev parent reply other threads:[~2011-01-17 17:39 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 [this message]
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
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=20110117173946.GL27123@htj.dyndns.org \
--to=tj@kernel.org \
--cc=James.Bottomley@suse.de \
--cc=herbert@13thfloor.at \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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).