From: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: jeff@garzik.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: add enclosure management support
Date: Fri, 18 Jan 2008 16:55:25 -0800 [thread overview]
Message-ID: <20080118165525.57749ac8@appleyard> (raw)
In-Reply-To: <1200703638.3111.95.camel@localhost.localdomain>
On Fri, 18 Jan 2008 18:47:18 -0600
James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> On Fri, 2008-01-18 at 16:35 -0800, Kristen Carlson Accardi wrote:
> > > Unfortunately, all the dual SAS/SATA enclosures seem to be coming
> > > with either SGPIO devices or full fledged SES-2 devices. I've
> > > actually got both (a backplane with SGPIO and an internal
> > > SAS/SATA enclosure with SES-2). Unfortunately, I don't have the
> > > necessary information to drive the SGPIO one ... it's connected
> > > directly to an aix94xx using the mini4i SGPIO signals ... I think
> > > aic94xx can drive them, we just don't have the programming
> > > information. The other is a standard SES-2 device, which I think
> > > I might be able to get working.
> > >
> >
> > Having documentation would be pretty helpful :). I know for ICH8,
> > if you read the docs it says that it supports SGPIO as well. But
> > then you realize it supports SGPIO via the LED protocol, wired up
> > to translate LED to SGPIO via hardware. But, even if it did
> > support straight SGPIO, this design can accommodate that. Can we
> > see the documentation for the SES-2 device?
>
> Yes, sure; SES-2 is here (usual place, since it's a SCSI standard):
>
> http://www.t10.org/ftp/t10/drafts/ses2/ses2r19a.pdf
>
> SGPIO is more convoluted. The canonical link is
> http://www.sffcommittee.com/ but that just seems to send you back to
> seagate. The actual standard is this one:
>
> ftp://ftp.seagate.com/sff/SFF-8485.PDF
>
> James
>
>
No, I meant for the actual device. The specs don't help all that much
in the area of actually transmitting the messages at the driver level -
at least they don't for AHCI.
next prev parent reply other threads:[~2008-01-19 1:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 0:44 [PATCH] libata: add enclosure management support Kristen Carlson Accardi
2008-01-17 22:50 ` James Bottomley
2008-01-17 23:36 ` Kristen Carlson Accardi
2008-01-18 1:55 ` Jeff Garzik
2008-01-18 16:52 ` Kristen Carlson Accardi
2008-01-18 17:11 ` James Bottomley
2008-01-18 17:41 ` Kristen Carlson Accardi
2008-01-19 0:16 ` James Bottomley
2008-01-19 0:35 ` Kristen Carlson Accardi
2008-01-19 0:47 ` James Bottomley
2008-01-19 0:55 ` Kristen Carlson Accardi [this message]
2008-01-19 2:33 ` James Bottomley
2008-01-19 0:52 ` Kristen Carlson Accardi
2008-01-21 18:12 ` James Bottomley
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=20080118165525.57749ac8@appleyard \
--to=kristen.c.accardi@intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jeff@garzik.org \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.