From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 10 23:34:34 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 73B8516A4CE for ; Mon, 10 Jan 2005 23:34:34 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2306D43D45 for ; Mon, 10 Jan 2005 23:34:34 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from mailnull by anduin.net with dspam-scanned (Exim 4.43 (FreeBSD)) id 1Co93Q-000Lcr-Ve for freebsd-amd64@freebsd.org; Tue, 11 Jan 2005 00:34:32 +0100 Received: from mailnull by anduin.net with spamassassin-scanned (Exim 4.43 (FreeBSD)) id 1Co93O-000Lck-Cy for freebsd-amd64@freebsd.org; Tue, 11 Jan 2005 00:34:32 +0100 Received: from localhost ([127.0.0.1]) by anduin.net with esmtp (Exim 4.43 (FreeBSD)) id 1Co93O-000Lch-6m for freebsd-amd64@freebsd.org; Tue, 11 Jan 2005 00:34:30 +0100 Message-ID: <41E31103.1040003@anduin.net> Date: Tue, 11 Jan 2005 00:34:27 +0100 From: =?ISO-8859-1?Q?Eirik_=D8verby?= User-Agent: Mozilla Thunderbird 1.0RC1 (Macintosh/20041201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on anduin.net X-Spam-Level: X-Spam-Status: No, hits=-5.9 required=7.5 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.1 Subject: asr on amd64 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: Mon, 10 Jan 2005 23:34:34 -0000 [Trying again, first attempt didn't come through, it seems. Otherwise excuse the dup.] Hi! Daring as I am, here's another attempt at having someone look into the asr driver and why it doesn't work on amd64. I have such a Zero-Channel RAID card laying around collecting dust, whereas it was planned installed in a server here long time ago. I know Scott Long looked into it long ago, and he seems to have been the last one to touch the driver. He indicated a few months ago that he had little time; perhaps things look brighter now that 5.3 is out? I'll cross-post to -current/-stable in a few days if I don't hear anything.. Thanks, /Eirik