From: Douglas Gilbert <dougg@torque.net>
To: brking@us.ibm.com
Cc: jgarzik@pobox.com,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
'SCSI Mailing List' <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@steeleye.com>
Subject: Re: [PATCH 0/6] libata: Support SATA attached via SAS
Date: Wed, 07 Jun 2006 13:09:34 -0400 [thread overview]
Message-ID: <4487084E.7090307@torque.net> (raw)
In-Reply-To: <4486FDBD.9030200@us.ibm.com>
Brian King wrote:
> Jeff,
>
> Here is a refresh of my patchset to allow SAS HBAs to use libata to
> control attached SATA devices. It should apply cleanly to #upstream.
>
> James,
>
> After our discussion at the storage summit I think I have
> a better idea what you are looking for with a SATA transport class.
> Unfortunately, the problem I am facing is that I am dealing with a
> firmware stack (ipr) which does not expose the physical transport
> to the host. The ipr firmware does all the device discovery and reports
> a configuration table describing the attached devices, but does not
> export any physical topology information. At some point in the future
> I hope to be able to extract this information from the ipr firmware
> stack and convert ipr to be able to utilize the sas/sata transport class,
> but, unfortunately, the firmware interfaces to accomplish this
> aren't available at this time.
Brian,
Does that mean that it doesn't have an SMP pass through?
SMP and the SAS addresses attached to the phys on the HBA
is enough to do discovery in the user space.
Doug Gilbert
next prev parent reply other threads:[~2006-06-07 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 16:24 [PATCH 0/6] libata: Support SATA attached via SAS Brian King
2006-06-07 17:09 ` Douglas Gilbert [this message]
2006-06-07 17:56 ` Brian King
2006-06-08 3:49 ` Douglas Gilbert
2006-06-08 13:32 ` Brian King
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=4487084E.7090307@torque.net \
--to=dougg@torque.net \
--cc=James.Bottomley@steeleye.com \
--cc=brking@us.ibm.com \
--cc=jgarzik@pobox.com \
--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).