From owner-cvs-src@FreeBSD.ORG Fri Jun 15 23:05:13 2007 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C8E0F16A468; Fri, 15 Jun 2007 23:05:13 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id A376A13C45E; Fri, 15 Jun 2007 23:05:13 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.14.1/8.14.1) with ESMTP id l5FN55ex004645; Fri, 15 Jun 2007 16:05:13 -0700 (PDT) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.14.1/8.14.1/Submit) with ESMTP id l5FN55lD004642; Fri, 15 Jun 2007 16:05:05 -0700 (PDT) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Fri, 15 Jun 2007 16:05:05 -0700 (PDT) From: mjacob@freebsd.org To: Peter Wemm In-Reply-To: <200706152258.l5FMwEfm089552@repoman.freebsd.org> Message-ID: <20070615160418.V4609@ns1.feral.com> References: <200706152258.l5FMwEfm089552@repoman.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/i386/isa clock.c src/sys/amd64/isa clock.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2007 23:05:13 -0000 Ooh, cool. This is crucial when you want to do a persistent 'failed' state for cheap machines with memory errors that you are using as appliances. Can you MFC these? > peter 2007-06-15 22:58:14 UTC > > FreeBSD src repository > > Modified files: > sys/i386/isa clock.c > sys/amd64/isa clock.c > Log: > Prototype (but functional) Linux-ish /dev/nvram interface to the extra > 114 bytes of cmos ram in the PC clock chip. The big difference between > this and the Linux version is that we do not recalculate the checksums > for bytes 16..31. > > We use this at work when cloning identical machines - we can copy the > bios settings as well. Reading /dev/nvram gives 114 bytes of data but > you can seek/read/write whichever bytes you like. > > Yes, this is a "foot, gun, fire!" type of device. > > Revision Changes Path > 1.232 +99 -0 src/sys/amd64/isa/clock.c > 1.237 +99 -0 src/sys/i386/isa/clock.c >