Subject: Re: device driver sysctls
To: None <tech-kern@NetBSD.org>
From: David Young <dyoung@pobox.com>
List: tech-kern
Date: 03/05/2004 11:52:22
On Fri, Mar 05, 2004 at 12:57:43PM +0900, YAMAMOTO Takashi 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>
> > > 
> > > How is that?
> > > 
> > > For me, driver.ath0 as an alternative to driver.ath.0 also has merit,
> > > because it parallels ifconfig arguments and such.
> > 
> > BTW, hw.ath and hw.ath0 are the FreeBSD style.
> > 
> > Dave
> 
> why do you need to use sysctl?  isn't ioctl enough?
> having two similar paths to a device driver seems redundant to me.

There is no existing ioctl that is suitable, so I will have to add a
new one.  If I add a new ioctl, then I need to add/modify a utility to
manipulate the ioctl. sysctl is comparatively simple.

Dave

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