Date: Wed, 24 May 2006 09:26:59 -0600 (MDT) From: Warner Losh <imp@bsdimp.com> To: Yuriy.Tsibizov@gfk.ru Cc: freebsd-multimedia@FreeBSD.org, des@des.no, freebsd-current@FreeBSD.org, Alexander@Leidinger.net Subject: Re: Call for testing: emu10kx driver for Creative sound cards Message-ID: <20060524.092659.74738447.imp@bsdimp.com> In-Reply-To: <D6B2C454E5A77B4D8DA0B863D3D6D492CC3458@demon.hhp.local>
index | next in thread | previous in thread | raw e-mail
From: "Yuriy Tsibizov" <Yuriy.Tsibizov@gfk.ru> Subject: RE: Call for testing: emu10kx driver for Creative sound cards Date: Wed, 24 May 2006 14:39:57 +0400 > > + .Pp > > + Sysctl nodes provided by drivers should not be considered to be > > + permanant unless they are documented in the driver's man page. > > + Names which start with _ denote a tree or node which is considered > > + impermanant and should not be relied up by code elsewhere in the > > + system. > > + Driver writers should use the sysctl infrastructure provided by > > + .Xr device_get_sysctl_ctx 9 > > + and > > + .Xr device_get_sysctl_tree 9 > > + for their sysctls. > > + Drivers should migrate from past interfaces to this new > > interface, but > > + provide, where needed, backwards compatibility shims. > > + These facilities export the sysctl as > > dev.<driver-name>.<unit>.attribute. > > Should sound drivers (pcm* device) be documented as an exception from this? > They use snd_sysctl_tree_top() to get tree OID under hw.snd.pcmX and > snd_sysctl_tree() to get their context. No. They should not. They should provide the old compatibility stuff in the old place, but also provide it in the correct place. Warnerhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060524.092659.74738447.imp>