From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 6 07:58:55 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64F9A16A4CE for ; Sat, 6 Mar 2004 07:58:55 -0800 (PST) Received: from hak.cnd.mcgill.ca (hak.cnd.mcgill.ca [132.216.11.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0B8743D1F for ; Sat, 6 Mar 2004 07:58:54 -0800 (PST) (envelope-from mat@hak.cnd.mcgill.ca) Received: from hak.cnd.mcgill.ca (localhost [127.0.0.1]) by hak.cnd.mcgill.ca (8.12.9/8.12.8) with ESMTP id i26G0oCR053619; Sat, 6 Mar 2004 11:00:50 -0500 (EST) (envelope-from mat@hak.cnd.mcgill.ca) Received: (from mat@localhost) by hak.cnd.mcgill.ca (8.12.9/8.12.8/Submit) id i26G0n2C053618; Sat, 6 Mar 2004 11:00:49 -0500 (EST) Date: Sat, 6 Mar 2004 11:00:49 -0500 From: Mathew Kanner To: Daniel Lang Message-ID: <20040306160049.GH35653@cnd.mcgill.ca> References: <20040303160340.700C5170D4@www.wcborstel.nl> <20040304205210.GJ490@geekpunk.net> <20040305184424.GA10310@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040305184424.GA10310@atrbg11.informatik.tu-muenchen.de> User-Agent: Mutt/1.4.1i Organization: I speak for myself, operating in Montreal, CANADA X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.62 X-Spam-Checker-Version: SpamAssassin 2.62 (2004-01-11) on hak.cnd.mcgill.ca cc: David Raistrick cc: hackers@freebsd.org Subject: Re: Standard sbc and pcm support in GENERIC kernel? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 15:58:55 -0000 On Mar 05, Daniel Lang wrote: > Hi, > > David Raistrick wrote on Fri, Mar 05, 2004 at 08:27:56AM -0800: > [..] > > kldload snd_driver > > > > is of course the correct way to do it. FWIW, kldunload snd_driver does > > /not/ unload all of the modules that kldload snd_driver loads. > [..] > > snd_driver is a module that contains _all_ drivers, > thus you have the best chance to get sound working. > Unloading it, will of course unload the whole module with > all drivers. There is no way to leave one of the drivers > in the kernel. > > I agree, that there is not much documentation which driver > module supports which sound device (or I was not successful > to dig that up). > > However, you can determine the correct module, by subsequently > loading and unloading each individual driver module. The one > which attached to your sound device and actually works > (check /dev/sndstat as well) is obviously the correct one. > > Not a very efficient way, but it works. :) David and Daniel, First let me say that on my 5.x machine, kldunload snd_driver does unload all the modules (and detaches the drivers when applicable). In regards to how hard it is to know which module provides the driver, I've just added to -current the following, mat@tube$ cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: at io 0xb800 irq 11 kld snd_cmi (1p/1r/0v channels duplex default) pcm1: at io 0xb400 irq 5 kld snd_emu10k1 (4p/2r/0v channels duplex) So the installation procedure is, as root. kldload snd_driver for each kld xxx in the output echo "xxx_load=\"YES\"" >> /boot/loader.conf Does this seem reasonable? --Mat -- In general, a standard is very useful, whether it's de facto or du jour. - Microsoft's Greg Sullivan as misquoted by News.Com