From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 16:50:49 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9F6216A4CE for ; Tue, 19 Apr 2005 16:50:49 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55E3243D53 for ; Tue, 19 Apr 2005 16:50:49 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3JGqtDV082513; Tue, 19 Apr 2005 10:52:55 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42653622.2070401@samsco.org> Date: Tue, 19 Apr 2005 10:47:30 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gary Mu1der References: <4264D40C.9050604@melange-it.nl> <42651FDC.405@samsco.org> <426524A2.9000600@infotechfl.com> In-Reply-To: <426524A2.9000600@infotechfl.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: supermicro X6DHP-8G2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2005 16:50:49 -0000 Gary Mu1der wrote: > Scott, > > I just determined that aaccli is not supported under amd64 for aac based > h/w RAID (specifically my Adaptec 2200S RAID controller). > > Any idea if or how much work will be required for aaccli to be supported > under amd64? Hmm, good question. The FreeBSD aaccli that I provided way back when was statically linked against FreeBSD 4.4 libraries, so I guess that our i386 emulation would need to be able to handle that (and specifically some of the quirks in how libc_r worked back then). For fun, you might try compiling a kernel with COMPAT_LINUX32 and AAC_COMPAT_LINUX and running the linux aaccli under it. I can't think of a reason why it wouldn't work, but I haven't tried it myself. Scott