From owner-freebsd-arch@FreeBSD.ORG  Thu Sep 23 14:52:39 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 40FCF16A4CE; Thu, 23 Sep 2004 14:52:39 +0000 (GMT)
Received: from athena.softcardsystems.com (mail.softcardsystems.com
	[12.34.136.114])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A60C443D55; Thu, 23 Sep 2004 14:52:38 +0000 (GMT)
	(envelope-from sah@softcardsystems.com)
Received: from athena (athena [12.34.136.114])i8NFpxtX020317;
	Thu, 23 Sep 2004 10:52:00 -0500
Date: Thu, 23 Sep 2004 10:51:59 -0500 (EST)
From: Sam <sah@softcardsystems.com>
X-X-Sender: sah@athena
To: Julian Elischer <julian@elischer.org>
In-Reply-To: <41508FEB.6030203@elischer.org>
Message-ID: <Pine.LNX.4.60.0409231044380.19882@athena>
References: <Pine.LNX.4.60.0409211531450.32120@athena>
	<415083CC.7C041DFD@freebsd.org><41508827.8010007@elischer.org>
	<41508FEB.6030203@elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
cc: Andre Oppermann <andre@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 14:52:39 -0000

>>> I'm sure you mentionned this before, but why ar eyou not doing it against 
>>> -current first?
>>> 
>>> We generally don't allow changes to 4.x untill they have settled a bit in 
>>> -current.  (or 5.x)

I'm about to update the coraid web site announcing support
for freebsd 4.x and would like to at least get a major number
assigned so customers don't start running the patch with
major 200.  Is this possible in advance of incorporation into
the kernel?

I'm hoping to have a 5.x driver ready in the next month or two,
probably patched against 5.3-stable when it's ready.

Cheers,

Sam