Setting the date/time does not always properly write-back the RTC, causing
authorMatthew Dillon <dillon@dragonflybsd.org>
Sun, 4 Apr 2004 08:00:06 +0000 (08:00 +0000)
committerMatthew Dillon <dillon@dragonflybsd.org>
Sun, 4 Apr 2004 08:00:06 +0000 (08:00 +0000)
commit2f70966e6d1cc1d1cb974c2f64b5d16941ec688e
treee6fd9532cf28bf5eaee44efbcd49304971eb75ca
parentf0f3e4e67e860d593c39ee683e325e966d82b7c8
Setting the date/time does not always properly write-back the RTC, causing
the date/time to be wrong again after a reboot.  This was due to the recent
systimer changes which updated the 'time_second' global via hardclock() only.
Change the writeback code to use microtime() instead of time_second.

Reported-by: esmith <esmith@patmedia.net>
sys/i386/isa/clock.c
sys/platform/pc32/isa/clock.c