From owner-freebsd-stable Fri Oct 23 15:08:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16453 for freebsd-stable-outgoing; Fri, 23 Oct 1998 15:08:22 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16448 for ; Fri, 23 Oct 1998 15:08:20 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01577; Fri, 23 Oct 1998 15:10:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810232210.PAA01577@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: chad@dcfinc.com cc: mike@smith.net.au (Mike Smith), Don.Lewis@tsc.tdk.com, freebsd-stable@FreeBSD.ORG Subject: Re: ECC memory support In-reply-to: Your message of "Fri, 23 Oct 1998 14:55:15 PDT." <199810232155.OAA21667@freebie.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Oct 1998 15:10:10 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> On Oct 22, 4:19pm, Mike Smith wrote: > >> } Subject: Re: ECC memory support > > The BIOS does. The kernel doesn't know anything about system management > > mode (SMM) or the system management interrupt (SMI), and it shouldn't, > > as it's specifically designed to allow the BIOS to obtain control while > > the system is running in order to perform system-specific tasks. > > Is there any formal documentation, or standards for SMM? Does each > motherboard have it's own specific BIOS and/or drivers? SMM is described in the processor manuals from Intel and friends. SMM-related features are usually discussed in the documentation for the device(s) in question. > I have 2.2-stable up on an AST Manhattan D file server. It documents a lot > of SMM features in the hardware. Cover tamper switches, under and over > voltage monitors, fan motor monitors, temperature monitoring, etc. > > It would be good to be able to get to those features, and to invoke a > powerdown under some failure conditions. You don't get to the features; you use the BIOS interface (DMI or SMBIOS) if you're lucky, or motherboard-specific drivers otherwise. We're attacking the problem from several different angles; the iicbus code provides the infrastructure for talking directly to many of the peripherals involved. We're also growing kernel infrastructure to call the relevant BIOS functions. Developers for these projects are definitely wanted. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message