> GPS has no bits for Daylight Savings. As far as I know only WWV and WWVB > have those bits. So for a clock displaying local time WWVB is the way to go.
WWVB's DST data is targeted at the US. Does anybody know how many other places use the same rules? What does Canada do? Has anybody looked into how much code it takes to implement DST? If you are willing to stick to one set of rules, you could pre-compute a small table to cover the next 20 (or 100) years. That's probably not good enough for a product, but OK for most home brew clocks. Can I get to 2100 with only 28 slots? (7 for day-of-week, and 4 for leap years) The full Unix time conversion package is pretty big if you are of running it on a tiny SOC. Has anybody implemented a slimmed down version? How slim can you get if all you want is DST? Besides, GPS gives you leap second warning. A while ago, somebody asked why use WWVB rather than GPS? One answer is so we can monitor what it does when a leap second happens. -- These are my opinions. I hate spam. _______________________________________________ time-nuts mailing list -- time-nuts@lists.febo.com To unsubscribe, go to http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com and follow the instructions there.
