From owner-freebsd-arch@FreeBSD.ORG  Thu Sep 23 21:14:09 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 90E0B16A4CE; Thu, 23 Sep 2004 21:14:09 +0000 (GMT)
Received: from athena.softcardsystems.com (mail.softcardsystems.com
	[12.34.136.114])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 43A0343D53; Thu, 23 Sep 2004 21:14:09 +0000 (GMT)
	(envelope-from sah@softcardsystems.com)
Received: from athena (athena [12.34.136.114])i8NMDTAc022627;
	Thu, 23 Sep 2004 17:13:29 -0500
Date: Thu, 23 Sep 2004 17:13:29 -0500 (EST)
From: Sam <sah@softcardsystems.com>
X-X-Sender: sah@athena
To: Julian Elischer <julian@elischer.org>
In-Reply-To: <41532FA0.6030405@elischer.org>
Message-ID: <Pine.LNX.4.60.0409231620240.19882@athena>
References: <Pine.LNX.4.60.0409211531450.32120@athena>
 <41508FEB.6030203@elischer.org><20040923191423.GE61631@FreeBSD.org>
 <Pine.LNX.4.60.0409231519030.19882@athena> <41532FA0.6030405@elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
cc: re@freebsd.org
cc: freebsd-arch@freebsd.org
Subject: Re: AoE for 4.x
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Sep 2004 21:14:09 -0000

On Thu, 23 Sep 2004, Julian Elischer wrote:

> I think that if you have a working driver we can assign you a number.
> I do have some questions however..
>
> this is AoE.. is it not possible at all to combne it with either the CAM
> framework (such as the atapicam stuff) or the existing ATA stuff..
> Don't take this the wrong way.. it's just a question..
> CAM is being used to talk to drives over firewire, usb, ata, scsi, 
> fibrechannel.
> it would seem that to unify this would be something that we should look at..
> Of course CAM itslef is showing its age in soem places and it could do with 
> some work itself..

It might be possible to plug into the CAM; I only briefly
glanced at it and it didn't appear appropriate.  The ATA
layer definitely isn't as parts of ATA don't make sense
in this context (Read DMA, Read Multiple, eg) and AoE
devices don't conform to the simple hardware probe/attach
methodology (as I understand it).

I would love to be proved wrong.  I'm always willing to
try a new approach if it's demonstrably better.

Sam