On 10/07/2014 08:48 AM, Noé RUBINSTEIN wrote: >> Sure, hwclock already has the ability to track the offset between the >> Hardware Clock and the System Clock(which presumably is the 'correct' time). > ...but this information is recorded only when setting the hardware > clock, which is impossible on some (arguably buggy) targets. I would think we should fix that. What hardware is it that hwclock cannot set the Hardware Clock? > >> With my patch, hctosys will include the offset when setting the System >> Clock. Which is the functionality you want, right? > Nearly. > > I guess in order for the use-case I want to be possible we would need > an option for --systohc/--set to modify the adjtime file, but not to > touch the hardware clock. Well, we could (re)calculate the drift factor even if setting the Hardware Clock fails, or have an option to (re)calculate without setting the HW Clock. I am willing to write such a patch if Mr. Zak approves. > -- > To unsubscribe from this list: send the line "unsubscribe util-linux" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
