From owner-freebsd-hackers Wed Aug 2 11:32:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-42.dsl.snfc21.pacbell.net [63.202.177.42]) by hub.freebsd.org (Postfix) with ESMTP id E0DDA37BE5F for ; Wed, 2 Aug 2000 11:32:28 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id LAA01035; Wed, 2 Aug 2000 11:43:17 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008021843.LAA01035@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Sayer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ESS Solo driver almost there (was Re: US$100 prize for adding ESS Audiodrive support to pcm) In-reply-to: Your message of "Wed, 02 Aug 2000 01:22:05 PDT." <3987DA2D.6A2EB8FC@quack.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Aug 2000 11:43:17 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does anyone know how one might place a restriction on a PCM driver's DMA > buffer > that it not cross a (physical) 64k boundary? The 'boundary' argument to bus_dma_tag_create() exists for this purpose. When you're setting up the tag before calling bus_dmamem_alloc() to actually allocate the memory, you can stipulate alignment and boundary constraints. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message