From owner-freebsd-current@FreeBSD.ORG Mon Oct 2 16:53:38 2006 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0D7916A403; Mon, 2 Oct 2006 16:53:38 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E35943D79; Mon, 2 Oct 2006 16:53:35 +0000 (GMT) (envelope-from xcllnt@mac.com) Received: from mac.com (smtpin01-en2 [10.13.10.146]) by smtpout.mac.com (Xserve/8.12.11/smtpout06/MantshX 4.0) with ESMTP id k92GrY1Y017065; Mon, 2 Oct 2006 09:53:35 -0700 (PDT) Received: from [192.168.1.2] (c-67-164-11-148.hsd1.ca.comcast.net [67.164.11.148]) (authenticated bits=0) by mac.com (Xserve/smtpin01/MantshX 4.0) with ESMTP id k92GrVWX025324 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 2 Oct 2006 09:53:32 -0700 (PDT) In-Reply-To: <20061002205039.301fa766.ariff@FreeBSD.org> References: <59493.1159791753@critter.freebsd.dk> <20061002205039.301fa766.ariff@FreeBSD.org> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <4CBB154F-6BD9-4E32-9A80-7A07ECC6B096@mac.com> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Mon, 2 Oct 2006 09:52:31 -0700 To: Ariff Abdullah X-Mailer: Apple Mail (2.752.3) X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Cc: "current@freebsd.org" Subject: Re: sound/driver/hda and ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2006 16:53:38 -0000 On Oct 2, 2006, at 5:50 AM, Ariff Abdullah wrote: > On Mon, 02 Oct 2006 12:22:33 +0000 > Poul-Henning Kamp wrote: >> >> During a "make universe" ia64 fails with the following errors. >> >> I wouldn't expect a sound driver to call any of those functions at >> all, what's going on ? *snip* > I wish BUS_DMA_NOCACHE has real meaning (like what NetBSD did) since > uncached DMA is pretty much guarantee to make the driver works on > broken i386/amd86 hardwares. > > Should we just narrow this down to i386/amd64 , or give > BUS_DMA_NOCACHE a real meaning as part of bus_dmamem_alloc() ? Ideally, we should fix our busdma implementation. In the mean time, feel free to make this driver specific to i386/amd64 because it now actually is specific to i386/amd64 and a broken make universe is a bother to other developers. Just my $0.02 -- Marcel Moolenaar xcllnt@mac.com