Date: Tue, 4 Dec 2001 22:56:08 -0600 From: Mike Meyer <mwm@mired.org> To: mikea <mikea@mikea.ath.cx> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SMP beeping Message-ID: <15373.43240.606521.16196@guru.mired.org> In-Reply-To: <20011204180025.A30499@mikea.ath.cx> References: <20011203185252.A336@colnta.acns.ab.ca> <3C0CDF53.946F926@mitre.org> <20011204091024.B3086@colnta.acns.ab.ca> <3C0CFB80.5C4BB9A9@mitre.org> <nospam-1007488821.44549@bambi.gbch.net> <20011204173850.A3320@twincat.vladsempire.net> <15373.24310.984664.86548@guru.mired.org> <001601c17d1d$cf7ec5c0$0ae48486@mizar> <20011204180025.A30499@mikea.ath.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
mikea <mikea@mikea.ath.cx> types: > On Tue, Dec 04, 2001 at 05:45:50PM -0600, Jim King wrote: > > > That's true for *all* the hardware monitoring utilities in the > > > ports. We really need a system that allows such things to be > > > independent of the hardware. > > Or at least something that works with recent hardware (e.g. Via 686 south > > bridge's hardware monitoring functions). > I've got some code about 10% hacked into shape. It's non-trivial > to autodetect the chipset, so I'm requiring the user to provide > config information. The various chips are incompatible in some > subtle ways as well as in the more obvious ways. I can test it for you if you when you get further into it. I'd even be interested in helping write the stuff, as I've been over the various of the tools that do this kind of thing. > I'd love to build an extensible framework so that one could just > build new adapter routines to read from the new chips as they > become available, and have the new routine(s) put data into > standard and invariant places for display and monitoring. That's > what I hope to do, anyway. Personally, I believe that this stuff belongs in the kernel. You add an option for the appropriate chipset when you build your custom kernel. The information then becomes available via a collection of sysctls that live under "hw.". That provides a way for the user to specify which chipset they have, and means that the tools that read it don't have to run with the privs to grovel through memory. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15373.43240.606521.16196>