From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Lord Subject: Re: Acard ATP8620 2SATA / 1 IDE driver - AHCI.C Nov082007 Date: Thu, 08 Nov 2007 15:19:52 -0500 Message-ID: <47336F68.2080601@rtr.ca> References: <47270656.7080205@garzik.org> <003701c81c63$cee89c30$6200a8c0@jameshsu> <025c01c82016$fbcf3810$d400a8c0@laurence> <025001c82067$d76c04c0$6200a8c0@jameshsu> <20071107221355.GB15784@havoc.gtf.org> <001f01c821b0$20b6c9f0$6200a8c0@jameshsu> <02d301c821e2$25dc01c0$d400a8c0@laurence> <005e01c821fb$502be120$6200a8c0@jameshsu> <20071108162229.GB31492@havoc.gtf.org> <473368FA.4030603@rtr.ca> <20071108200920.GB4895@havoc.gtf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from rtr.ca ([76.10.145.34]:1629 "EHLO mail.rtr.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756082AbXKHUTy (ORCPT ); Thu, 8 Nov 2007 15:19:54 -0500 In-Reply-To: <20071108200920.GB4895@havoc.gtf.org> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Jeff Garzik Cc: IDE/ATA development list , Tejun Heo , Alan Cox Jeff Garzik wrote: > On Thu, Nov 08, 2007 at 02:52:26PM -0500, Mark Lord wrote: >> Jeff Garzik wrote: >>> .. >>> 2) This chip includes target mode support. Very nice, well done! >>> I hope that standard AHCI eventually supports this nice feature! >> .. >> >> Speaking of which. Do we have a strategy as to how to implement/support >> the target side of target mode on controllers which can do it? >> >> The Marvell chips also have a target mode feature, and I'd like to add >> support for it soon-ish, but it's now clear how you would like it plumbed >> into libata. >> >> It's almost like a separate driver/subsystem, except that would be very >> silly. > > I'm letting the SCSI folks do the heavy lifting, implementing SCSI > target mode -- an effort already quite well along. > > We should be able to piggyback off of that work. .. MMmm.. I wonder what the most common use case is for target mode? Everybody I've dealt with thus far uses it as a high-speed local comms interface, which would suggest that it might be done as a network interface (ethernet emulation). But that would confusingly go across driver subsystems, despite that this is how it actually is used.