From owner-freebsd-hackers Mon Jul 21 09:58:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA24194 for hackers-outgoing; Mon, 21 Jul 1997 09:58:02 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA24173; Mon, 21 Jul 1997 09:57:55 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id JAA05307; Mon, 21 Jul 1997 09:57:51 -0700 (PDT) Message-Id: <199707211657.JAA05307@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@freebsd.org cc: multimedia@freebsd.org, Luigi Rizzo Subject: auto dma? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Jul 1997 09:57:51 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk luigi@labinfo.iet.unipi.it said: > I am looking at Mike's idea of using DMA_AUTOMODE and a circular > buffer, but unfortunately there are no support routines to read the > current transfer status from the dma registers and I have to write > them myself. This also means that the old sound driver probably did > not really work very reliably, and explains why someone was reporting > that pieces of sound were repeating multiple times. Does anyone know how to read the current number of bytes transferred in in a dma transfer? It will be kind of nice to know as a safe guard for cards which occasionlly fail to generate an interrupt and yes I do have such a card is the SB16... Tnks, Amancio