Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 7 Nov 2003 17:36:06 -0500
From:      Mathew Kanner <mat@cnd.mcgill.ca>
To:        Scott Long <scottl@freebsd.org>
Cc:        multimedia@freebsd.org
Subject:   Re: Re: HEADSUP: Soekris and generic LED/lamp support in FreeBSD-current
Message-ID:  <20031107223606.GI94805@cnd.mcgill.ca>
In-Reply-To: <20031107152814.Y51343@pooker.samsco.home>
References:  <Pine.NEB.3.96L.1031104210859.71158B-100000@fledge.watson.org> <20031107204812.GD374@arthur.nitro.dk> <20031107210525.GG34063@elvis.mu.org> <20031107152814.Y51343@pooker.samsco.home>

next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 07, Scott Long wrote:
> On Fri, 7 Nov 2003, Alfred Perlstein wrote:
> > * Simon L. Nielsen <simon@FreeBSD.org> [031107 12:48] wrote:
> > > On 2003.11.07 08:43:11 -0800, Bruce A. Mah wrote:
> > >
> > > > I encourage people interested in writing / importing manpages for these
> > > > drivers to self-organize on the doc@ list.  Note that even a "stub"
> > > > manual page with a one-line description of a driver and the
> > > > corresponding entries from the hardware notes would be of value.
> > >
> > > I have converted Bruce's list into a TODO list [1].  If anybody start
> > > writing one of the missing manual pages, please update the TODO list to
> > > avoid duplicate work.
> > >
> > > [1] http://www.freebsd.org/docproj/current.html#sec4manualpages
> > > (after next web build)
> >
> > On the subject, there needs to be a sound(4) manpage that explains
> > exactly which module to load for each chipset.  Getting sound on
> > FreeBSD working isn't so cool.  While having the modules split up
> > into a dozen or so parts for different chipsets is cool from
> > an engineering perspective, it's pretty confusing to users.  Can't
> > we just have a "kldload sound" thing that will load them all?
> 
> We've had that for years. Loading snd_driver.ko loads all of the sound
> drivers.  Unloading it then unloads all of the drivers that didn't attach.
> I thought that it was documented somewhere but apparently it isn't.


	kldunload should unload all driver.  I plan to augment
/dev/sndstat to show which driver is actually behind the device.

	--Mat
-- 
	Having your book made into a movie is like having your ox
	made into a bouillon cube.
			- Bill Neely



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031107223606.GI94805>