Date: Fri, 31 Mar 2000 21:16:58 +0400 From: Grigoriy Strokin <grg@philol.msu.ru> To: Ken Marx <kmarx@bigshed.com> Cc: Grigoriy Strokin <grg@philol.msu.ru>, freebsd-multimedia@FreeBSD.ORG Subject: Re: 4.0/pci128/.wav's Message-ID: <20000331211658.A46206@isabase.philol.msu.ru> In-Reply-To: <38E4DC7E.68F651C9@bigshed.com>; from kmarx@bigshed.com on Fri, Mar 31, 2000 at 09:12:30AM -0800 References: <38E4D68F.5CD558DC@bigshed.com> <20000331205142.B45857@isabase.philol.msu.ru> <38E4DC7E.68F651C9@bigshed.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 31, 2000 at 09:12:30AM -0800, Ken Marx wrote: > Hi Grigoriy, > > Very interesting. We've noticed that doing a cat file.au > /dev/audio > (or /dev/dsp) seems ok. Maybe there's something funky with the ioctl > support for one of the GET/SET_xxx commands? > > Have you by chance found a PCI sound card for which this bad behavior > *doesn't* occur? No, but I haven't tried much :) I was going to buy PCI128 because when I told to my friends that also run FreeBSD 4.0 about my PCI64 problems they said that they have PCI128, it works fine and they recomend all to buy it for FreeBSD. Now, however, I won't buy PCI128 :) > > I've got a sinking feeling that I'm going to be adding printf's to > the driver by next week sometime... bleh. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000331211658.A46206>