From owner-cvs-src@FreeBSD.ORG Thu Aug 31 16:16:25 2006 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1D3E16A4E6; Thu, 31 Aug 2006 16:16:24 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED47843D72; Thu, 31 Aug 2006 16:16:22 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k7VGGKdU024605 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 31 Aug 2006 09:16:22 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <44F70B54.1080800@errno.com> Date: Thu, 31 Aug 2006 09:16:20 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5.0.4 (X11/20060724) MIME-Version: 1.0 To: Christian Brueffer References: <200608310618.k7V6IkQC095302@repoman.freebsd.org> <44F704EA.60109@errno.com> <20060831160859.GB1758@haakonia.hitnet.RWTH-Aachen.DE> In-Reply-To: <20060831160859.GB1758@haakonia.hitnet.RWTH-Aachen.DE> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/modules Makefile X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2006 16:16:25 -0000 Christian Brueffer wrote: > On Thu, Aug 31, 2006 at 08:48:58AM -0700, Sam Leffler wrote: >> Christian Brueffer wrote: >>> brueffer 2006-08-31 06:18:46 UTC >>> >>> FreeBSD src repository >>> >>> Modified files: (Branch: RELENG_6) >>> sys/modules Makefile >>> Log: >>> MFC: rev. 1.482 + 1.483 >>> >>> Build ipw(4) and iwi(4) modules on i386 and amd64 only. >> FWIW I tested iwi on amd64 and it failed due to issues with the firmware >> modules (invalid relocation datum were being generated causing the >> system to blow up when loading the firmware). I never resolved this; it >> was waiting on a response from Peter. >> > > Hmm, ok. Do you think we should disable the module build for amd64 in > RELENG_6 for the time being? Did loading the firmware even work at some > point in time, or is this a recent issue? Disable. I doubt anyone but me has tried it. Sam