From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: dougg@torque.net, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: SATA on SAS [was: ATAPI cdrecord issue 2.5.67]
Date: Fri, 11 Apr 2003 23:35:14 -0600 [thread overview]
Message-ID: <2301930000.1050125714@aslan.btc.adaptec.com> (raw)
In-Reply-To: <3E97632F.1090104@torque.net>
> Spinning this discussion another way, with Serial Attached SCSI
> (SAS) real SATA disk drives can be attached to SAS host bus adapters
> (HBAs). For that matter cdwriters that use MMC (scsi instruction
> set) over ATAPI could be SATA devices connected to a SAS HBA.
Actually, SAS does not cover the case of a SAS HBA connected directly
to a SATA device. You must through an expander since SATA devices do
not speak STP and it is the expander that provides the STP -> SATA conversion
on the backend. The spec does not preclude a SAS HBA speaking SATA
directly, but in doing so, it will be operating outside of the SAS
spec.
--
Justin
prev parent reply other threads:[~2003-04-12 5:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 0:51 SATA on SAS [was: ATAPI cdrecord issue 2.5.67] Douglas Gilbert
2003-04-12 5:35 ` Justin T. Gibbs [this message]
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=2301930000.1050125714@aslan.btc.adaptec.com \
--to=gibbs@scsiguy.com \
--cc=dougg@torque.net \
--cc=linux-kernel@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