Date: Sun, 02 Apr 2000 13:22:49 -0700 From: Ken Marx <kmarx@bigshed.com> To: Grigoriy Strokin <grg@philol.msu.ru> Cc: freebsd-multimedia@FreeBSD.ORG Subject: Re: 4.0/pci128/.wav's Message-ID: <38E7AC19.54AE5A50@bigshed.com> References: <38E4D68F.5CD558DC@bigshed.com> <20000331205142.B45857@isabase.philol.msu.ru> <38E4DC7E.68F651C9@bigshed.com> <20000331211658.A46206@isabase.philol.msu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Two corrections to previous email from me on this topic: 1. Apparantly problem also occurs for cat of .au to /dev/dsp (or audio) (I'd claimed otherwise.) 2. My co-worker's 5.0 box has this same problem (I'd claimed it worked on his machine). Anyone know who supports the pcm driver? thanks, k. Grigoriy Strokin wrote: > > 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. -- Ken Marx, kmarx@bigshed.com Display leadership on the total value ratcheting!! - http://cgi.bigshed.com/~kmarx/cgi-bin/speak.cgi 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?38E7AC19.54AE5A50>