From owner-freebsd-multimedia@FreeBSD.ORG Wed Feb 9 16:40:11 2011 Return-Path: Delivered-To: freebsd-multimedia@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BB61106564A for ; Wed, 9 Feb 2011 16:40:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2F6008FC12 for ; Wed, 9 Feb 2011 16:40:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p19GeBIn041963 for ; Wed, 9 Feb 2011 16:40:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p19GeBMN041962; Wed, 9 Feb 2011 16:40:11 GMT (envelope-from gnats) Date: Wed, 9 Feb 2011 16:40:11 GMT Message-Id: <201102091640.p19GeBMN041962@freefall.freebsd.org> To: freebsd-multimedia@FreeBSD.org From: Garrett Cooper Cc: Subject: Re: kern/132848: [sound] [snd_emu10kx] driver problem with card init, snd_emu10k1 inits card correctly X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Garrett Cooper List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Feb 2011 16:40:11 -0000 The following reply was made to PR kern/132848; it has been noted by GNATS. From: Garrett Cooper To: Marius Strobl Cc: bug-followup@freebsd.org, rickard.granath@gmail.com Subject: Re: kern/132848: [sound] [snd_emu10kx] driver problem with card init, snd_emu10k1 inits card correctly Date: Wed, 9 Feb 2011 08:39:53 -0800 On Wed, Feb 9, 2011 at 8:26 AM, Marius Strobl w= rote: > On Wed, Feb 09, 2011 at 03:44:36AM -0800, Garrett Cooper wrote: >> =A0 =A0 This is probably fixed by r218478. > > Hrm, I actually doubt the problems described in PR 132848 are related > to what was fixed in r218478. The description of this PR sounds more > like issues with the hardware initialization. Good point. Rereading the problem description it probably isn't. Thanks! -Garrett