Subject: Re: device driver sysctls
To: None <tech-kern@NetBSD.org>
From: David Young <dyoung@pobox.com>
List: tech-kern
Date: 03/01/2004 22:25:02
On Mon, Mar 01, 2004 at 11:01:48PM -0500, Andrew Brown wrote:
> On Mon, Mar 01, 2004 at 12:46:07PM -0600, David Young wrote:
> >On Mon, Mar 01, 2004 at 10:11:53PM +1100, Daniel Carosone wrote:
> >> On Sun, Feb 29, 2004 at 08:08:04PM -0600, David Young wrote:
> >> > I've added sysctls for ath(4) in ath.* (that's right, top-level). I
> >> > don't intend for this to be permanent. Where do the sysctls belong?
> >> > I believe it was Dan Carosone who suggested,
> >> > 
> >> > 	driver.ath.<global variable>
> >> > 	driver.ath.0.<instance variable>
> >> 
> >> driver.ath.0 or dev.ath0 seems fine
> >> 
> >> btw, these sysctl's appear, with values in them, in a running GENERIC
> >> even though i have no ath(4) attached.  An oversight?
> >
> >I feel that ath.debug and ath.hal.debug (shows w/ options AH_DEBUG)
> >belong. I think that ath.outdoor influences device attachment, so it
> >should stay, also.
> 
> well...perhaps, but should they show up even if the device is not
> attached?

I was not clear, sorry.  If I am debugging device attachment, but the
ath.debug sysctl only appears *after* attachment, it is too late to
frob it.

Dave

-- 
David Young             OJC Technologies
dyoung@ojctech.com      Urbana, IL * (217) 278-3933