Date: Thu, 02 Feb 2006 00:25:58 -0500 From: Mike Jakubik <mikej@rogers.com> To: Andrew Reilly <andrew-freebsd@areilly.bpc-users.org> Cc: freebsd-amd64@freebsd.org Subject: Re: Driver failed to allocate 49152 bytes of DMA buffer? Message-ID: <43E197E6.4030302@rogers.com> In-Reply-To: <20060202050223.GA21154@gurney.reilly.home> References: <20060202040253.GA20444@gurney.reilly.home> <43E18BE6.4010502@rogers.com> <20060202050223.GA21154@gurney.reilly.home>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Reilly wrote: > On Wed, Feb 01, 2006 at 11:34:46PM -0500, Mike Jakubik wrote: > >> Andrew Reilly wrote: >> >>> What are the chances that there has been a regression of some >>> sort in this area since 6.0-RELEASE (which didn't boot on the >>> board because of ACPI issues that have since been fixed)? >>> >>> >> /usr/src/UPDATING: >> >> 20051230: >> A lot of fixes and new features in the soundsystem. To get all >> benefits, you may want to recompile mplayer (if installed) after >> booting the new world. >> >> >> Always read this file before updating. >> > > I'm afraid that I don't understand how this relates to my question. > Could you clarify, please? I'm not trying to use the native sound > drivers (they still don't support my envy24-based card), but rather > the third-party, closed-source driver from www.4front-tech.com. > > That UPDATING comment reads to me to refer to an ioctl API change > that affects user-land programs. I already have to deal with that > anyway, because the FreeBSD native sound drivers, and their APIs > have diverged somewhat from the original OSS (which is more or less > what the 4front driver supports). > I'm just saying that this may be the cause, since thats the only thing sound related thats changed since -RELEASE. Have you brought up the issue with 4front?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43E197E6.4030302>