From owner-freebsd-current  Wed Feb  7 06:10:16 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id GAA00820
          for current-outgoing; Wed, 7 Feb 1996 06:10:16 -0800 (PST)
Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.9.13])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA00809
          for <current@FreeBSD.ORG>; Wed, 7 Feb 1996 06:10:11 -0800 (PST)
Received: (from james@localhost) by miller.cs.uwm.edu (8.7.3/8.7.3) id IAA05624; Wed, 7 Feb 1996 08:10:09 -0600
Date: Wed, 7 Feb 1996 08:10:09 -0600
From: Jim Lowe <james@miller.cs.uwm.edu>
Message-Id: <199602071410.IAA05624@miller.cs.uwm.edu>
To: joerg_wunsch@uriah.heep.sax.de, root@deadline.snafu.de
Subject: Re: Tired of "isa_dmadone_nobounce" messages
Cc: current@FreeBSD.ORG
Sender: owner-current@FreeBSD.ORG
Precedence: bulk

The problem is that someone changed the isa.c dma_start code
and the sound code a week or so ago and didn't complete the
required changes.  They added the code to set dma_dusy[], but didn't
add the code to clear dma_busy[] in dmabuf.c.  Thus, the messages.

I hope this person will eventually fix what he broke or back out
his changes -- since it is effecting a lot of people who use this
code.

	-Jim