Date: Wed, 26 May 1999 09:38:22 -0700 (PDT) From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: imp@harmony.village.org (Warner Losh) Cc: mike@smith.net.au (Mike Smith), roger@cs.strath.ac.uk (Roger Hardiman), nick.hibma@jrc.it (Nick Hibma), roger@FreeBSD.org (Roger Hardiman), cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/conf options Message-ID: <199905261638.JAA97006@troutmask.apl.washington.edu> In-Reply-To: <199905261554.JAA02293@harmony.village.org> from Warner Losh at "May 26, 1999 09:54:17 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh wrote: > In message <199905261555.IAA87427@troutmask.apl.washington.edu> Steve Kargl writes: > : The sysctl varaibles become: > : > : hw.bus.pci0 = "82440FX" > : hw.bus.pci1 = NULL > : hw.bus.isa0 = "82371SB" > : hw.bus.isa1 = NULL > > You might want to look at the DEVICE_SYSCTLS kernel option. It does > something similar. I'm not sure if it is intended for "production" > use or not, but it sure is handy for debugging. > DEVICE_SYSCTLS is not documented in LINT, so I would suspect that it isn't meant for "production" use. If I understand Roger and Mike's requirement, they need to know chipset/bus information that must be available before their device drivers are probed. The question seems to be whether to store the information or reprobe the chipset/bus for each device. Sysctl seems (to me) to be a natural solution to the problem The only possible exception is whether number of possible busses to enumerate is large. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905261638.JAA97006>