From owner-freebsd-stable Tue Dec 4 16: 3:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mikea.ath.cx (okc-65-30-192-11.mmcable.com [65.30.192.11]) by hub.freebsd.org (Postfix) with ESMTP id 8595037B417 for ; Tue, 4 Dec 2001 16:03:20 -0800 (PST) Received: (from mikea@localhost) by mikea.ath.cx (8.11.6/8.11.1) id fB500PU30517; Tue, 4 Dec 2001 18:00:25 -0600 (CST) (envelope-from mikea) Date: Tue, 4 Dec 2001 18:00:25 -0600 From: mikea To: Jim King Cc: Mike Meyer , Josh Paetzel , Greg Black , Jason Andresen , Chad David , freebsd-stable@FreeBSD.ORG Subject: Re: SMP beeping Message-ID: <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><20011204173850.A3320@twincat.vladsempire.net> <15373.24310.984664.86548@guru.mired.org> <001601c17d1d$cf7ec5c0$0ae48486@mizar> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001601c17d1d$cf7ec5c0$0ae48486@mizar>; from jim@jimking.net on Tue, Dec 04, 2001 at 05:45:50PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Dec 04, 2001 at 05:45:50PM -0600, Jim King wrote: > "Mike Meyer" wrote: > > Josh Paetzel types: > > > > The idiotic results are all on very new machines, so I don't have > > > > much hope for this utility. > > > If you look at the man page for this utility, there are only a few > > > hardware monitoring chips that are supported. > > > > 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'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. -- Mike Andrews mikea@mikea.ath.cx Tired old sysadmin since 1964 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message