From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Justin T. Gibbs" Subject: Re: SATA on SAS [was: ATAPI cdrecord issue 2.5.67] Date: Fri, 11 Apr 2003 23:35:14 -0600 Sender: linux-scsi-owner@vger.kernel.org Message-ID: <2301930000.1050125714@aslan.btc.adaptec.com> References: <3E97632F.1090104@torque.net> Reply-To: "Justin T. Gibbs" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from magic-mail.adaptec.com ([208.236.45.100]:63208 "EHLO magic.adaptec.com") by vger.kernel.org with ESMTP id S263169AbTDLFYQ (for ); Sat, 12 Apr 2003 01:24:16 -0400 In-Reply-To: <3E97632F.1090104@torque.net> Content-Disposition: inline List-Id: linux-scsi@vger.kernel.org To: dougg@torque.net, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org > 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