Phil Endecott wrote: > Phil Endecott wrote: >> - Setting the clock takes up to a second. But I don't think it would >> if we didn't have to use --directisa. > > It turns out that it still takes up to a second even when hwclock is > reading from /dev/rtc; it still waits for the time to tick over to the > next second. Not using --directisa just means that it is idle wile > waiting for the tickover, rather than polling. It's still on the > critical path for the boot. > > I think I'd be quite happy for my clock to be +/- half a second, at > least until NTP has started, but hwclock doesn't seem to have an option > for this.
This patch: http://chezphil.org/tmp/hwclock-add-notickwait.patch adds a new option, --notickwait, to hwclock. This causes it to not wait for the hardware clock to tick over, saving on average half a second per invocation but meaning that your clock will be on average half a second out. Phil. _______________________________________________ Debian-eeepc-devel mailing list Debian-eeepc-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel