From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luben Tuikov Subject: Re: [PATCH] minimal SAS transport class Date: Fri, 19 Aug 2005 13:56:39 -0400 Message-ID: <43061D57.9060201@adaptec.com> References: <9BB4DECD4CFE6D43AA8EA8D768ED51C21D7A3A@xbl3.ma.emulex.com> <4304DBA1.4050900@pobox.com> <20050819140631.GB12485@lst.de> <43061C3C.2020303@adaptec.com> <20050819175459.GA16619@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from magic.adaptec.com ([216.52.22.17]:35496 "EHLO magic.adaptec.com") by vger.kernel.org with ESMTP id S965016AbVHSR4l (ORCPT ); Fri, 19 Aug 2005 13:56:41 -0400 In-Reply-To: <20050819175459.GA16619@lst.de> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Christoph Hellwig Cc: Jeff Garzik , James.Smart@Emulex.Com, jejb@steeleye.com, ltuikov@yahoo.com, Eric.Moore@lsil.com, andrew.patterson@hp.com, linux-scsi@vger.kernel.org On 08/19/05 13:54, Christoph Hellwig wrote: > On Fri, Aug 19, 2005 at 01:51:56PM -0400, Luben Tuikov wrote: > >>On 08/19/05 10:06, Christoph Hellwig wrote: >> >>>SATA support for SAS host adapters. Especially when talking STP to a >>>bridge this is a little more complicated than the current libata model. >>>That doesn't mean I don't want to share code and mechanisms but it'll >>>need a little refactoring at least. >> >>I'm not understanding what you mean here. >> >>If the lower level is implemented correctly, libata would >>just pick up and "drive" the ATA device. > > > Yes. But to get that to work we'll need to fix some assumptions in > libata, define proper interfaces between the SAS LLDD, the SAS transport > class and libata. It's doable and desirable, but it'll need some work. Do you have a SAS LLDD? Which one is it that will let you do this? Luben