From owner-freebsd-stable Sun Feb 28 15:24:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from geo.geocast.net (geo.geocast.net [128.177.240.120]) by hub.freebsd.org (Postfix) with ESMTP id 79475153D6 for ; Sun, 28 Feb 1999 15:24:35 -0800 (PST) (envelope-from castor@geocast.net) Received: from localhost (castor@localhost) by geo.geocast.net (8.8.8/8.8.8) with ESMTP id PAA19939 for ; Sun, 28 Feb 1999 15:24:41 -0800 (PST) Date: Sun, 28 Feb 1999 15:24:41 -0800 (PST) From: Castor Fu To: freebsd-stable@FreeBSD.ORG Subject: Re: bus_dmamap_load & compiler glitch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This looks like a usage error on my part. I was using what I thought was the default value for nsegments in the dma tag, and letting this propogate though. Unfortunately, the system then tried to allocate a very large array off of the stack which caused the problems I was seeing. Sorry for the confusion. -castor On Sat, 27 Feb 1999, Castor Fu wrote: > I'm trying to use the bus_dma interface with 3.1-RELEASE and > the bus_dmamap_load routine appears to compile incorrectly with > the default C compiler and default flags. > > It somehow fouls up in detecting the first segment and generates > two segments, the first of which is garbage. > > Has anyone seen anything like this? I realize these routines are > not used much yet in current drivers. > > Putting in a few printfs seems to get the compiler to do the right thing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message