Date: Fri, 15 Jun 2007 16:05:05 -0700 (PDT) From: mjacob@freebsd.org To: Peter Wemm <peter@freebsd.org> 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 Message-ID: <20070615160418.V4609@ns1.feral.com> In-Reply-To: <200706152258.l5FMwEfm089552@repoman.freebsd.org> References: <200706152258.l5FMwEfm089552@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070615160418.V4609>