From owner-freebsd-hackers Sun May 12 20:26:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA08956 for hackers-outgoing; Sun, 12 May 1996 20:26:31 -0700 (PDT) Received: from xi.dorm.umd.edu (root@xi.dorm.umd.edu [129.2.152.45]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA08937 for ; Sun, 12 May 1996 20:26:28 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by xi.dorm.umd.edu (8.7.5/8.6.12) with SMTP id XAA07216; Sun, 12 May 1996 23:26:15 -0400 (EDT) Date: Sun, 12 May 1996 23:26:14 -0400 (EDT) From: Sujal Patel X-Sender: smpatel@xi.dorm.umd.edu To: "Amancio Hasty Jr." cc: hackers@freebsd.org Subject: Re: snd in -current, vmix, misc In-Reply-To: <199605130320.UAA10431@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 12 May 1996, Amancio Hasty Jr. wrote: > Oh, I can call isa_dmadone however I think is a waste unless we intent > to shared dma channels and even then it makes no sense. I wonder > what the engineer who decided that we shall call isa_dmadone > after we get a dma interrupt after a call to isa_dmastart had in mind?? The last time I mucked around with the isadma stuff, I left the semantics of dma_busy alone. Currently, dmadone will just flip some flags and copy the bounce buffer if need be. This may change though, for example NetBSD does all sorts of things in isa_dmadone. Sujal