linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
	Tejun Heo <htejun@gmail.com>, Alan Cox <alan@redhat.com>
Subject: Re: Acard ATP8620 2SATA / 1 IDE  driver - AHCI.C Nov082007
Date: Thu, 08 Nov 2007 15:19:52 -0500	[thread overview]
Message-ID: <47336F68.2080601@rtr.ca> (raw)
In-Reply-To: <20071108200920.GB4895@havoc.gtf.org>

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.

  reply	other threads:[~2007-11-08 20:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00b501c81ace$ece895f0$6200a8c0@jameshsu>
2007-10-30 10:24 ` Should be Acard ATP8620 2SATA / 1 IDE driver Jeff Garzik
2007-11-01  8:47   ` jameshsu
     [not found]     ` <025c01c82016$fbcf3810$d400a8c0@laurence>
     [not found]       ` <025001c82067$d76c04c0$6200a8c0@jameshsu>
2007-11-07 22:13         ` Jeff Garzik
2007-11-07 22:16           ` Jeff Garzik
     [not found]           ` <001f01c821b0$20b6c9f0$6200a8c0@jameshsu>
     [not found]             ` <02d301c821e2$25dc01c0$d400a8c0@laurence>
2007-11-08 11:34               ` Re:Acard ATP8620 2SATA / 1 IDE driver - AHCI.C Nov082007 jameshsu
2007-11-08 16:22                 ` Acard " Jeff Garzik
2007-11-08 19:52                   ` Mark Lord
2007-11-08 20:09                     ` Jeff Garzik
2007-11-08 20:19                       ` Mark Lord [this message]
2007-11-08 20:31                         ` Jeff Garzik
2007-11-08 20:49                           ` SATA Target mode & libata Mark Lord
2007-11-08 21:05                             ` Jeff Garzik
2007-11-27 10:18                   ` Acard ATP8620 2SATA / 1 IDE driver - AHCI.C Nov082007 jameshsu
2007-11-07 22:30         ` [PATCH] Re: Should be Acard ATP8620 2SATA / 1 IDE driver Jeff Garzik
     [not found]           ` <005801c821fa$892827f0$6200a8c0@jameshsu>
2007-11-08 16:18             ` Jeff Garzik
2007-12-17  2:35 Acard ATP8620 2SATA / 1 IDE driver - AHCI.C Nov082007 jameshsu

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=47336F68.2080601@rtr.ca \
    --to=liml@rtr.ca \
    --cc=alan@redhat.com \
    --cc=htejun@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).