public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] RTC format
@ 2001-07-16 14:09 Trenton D. Adams
  2001-07-16 14:14 ` Trenton D. Adams
  0 siblings, 1 reply; 3+ messages in thread
From: Trenton D. Adams @ 2001-07-16 14:09 UTC (permalink / raw)
  To: 'eCos Discussion'

Is there a standard format for RTCs?  I don't know what to write to the
RTC 32-bit register to set it.  I came up with my own hh:mm:ss.xxx
format for storage in a 32 bit register, but I wonder if it's
compatible?  After all, I certainly hope it's not based on ms from some
date because it would only store 49.xxx days then.

bit   | measurement
_________________
27-23 | hours
22-17 | minutes
16-10 | seconds
9-0   | milliseconds

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: [ECOS] RTC format
  2001-07-16 14:09 [ECOS] RTC format Trenton D. Adams
@ 2001-07-16 14:14 ` Trenton D. Adams
  0 siblings, 0 replies; 3+ messages in thread
From: Trenton D. Adams @ 2001-07-16 14:14 UTC (permalink / raw)
  To: 'Trenton D. Adams', 'eCos Discussion'

I just noticed it's a 1Hz clock so I assume it's stored in seconds from
1980?  I don't think 49,710 years will be a problem! :)

  > -----Original Message-----
  > From: ecos-discuss-owner@sources.redhat.com 
  > [ mailto:ecos-discuss-owner@sources.redhat.com ] On Behalf Of 
  > Trenton D. Adams
  > Sent: Monday, July 16, 2001 3:10 PM
  > To: 'eCos Discussion'
  > Subject: [ECOS] RTC format
  > 
  > 
  > Is there a standard format for RTCs?  I don't know what to 
  > write to the RTC 32-bit register to set it.  I came up with 
  > my own hh:mm:ss.xxx format for storage in a 32 bit 
  > register, but I wonder if it's compatible?  After all, I 
  > certainly hope it's not based on ms from some date because 
  > it would only store 49.xxx days then.
  > 
  > bit   | measurement
  > _________________
  > 27-23 | hours
  > 22-17 | minutes
  > 16-10 | seconds
  > 9-0   | milliseconds
  > 
  > 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: [ECOS] RTC format
@ 2001-07-16 14:55 Trenton D. Adams
  0 siblings, 0 replies; 3+ messages in thread
From: Trenton D. Adams @ 2001-07-16 14:55 UTC (permalink / raw)
  To: 'Trenton D. Adams', 'eCos Discussion'

I forgot to divide by 365! :)  So, it's actually 136 years if anyone
cares.  I doubt they do.

  > -----Original Message-----
  > From: Trenton D. Adams [ mailto:tadams@extremeeng.com ] 
  > Sent: Monday, July 16, 2001 3:15 PM
  > To: 'Trenton D. Adams'; 'eCos Discussion'
  > Subject: RE: [ECOS] RTC format
  > 
  > 
  > I just noticed it's a 1Hz clock so I assume it's stored in 
  > seconds from 1980?  I don't think 49,710 years will be a problem! :)
  > 
  >   > -----Original Message-----
  >   > From: ecos-discuss-owner@sources.redhat.com 
  >   > [ mailto:ecos-discuss-owner@sources.redhat.com ] On Behalf Of 
  >   > Trenton D. Adams
  >   > Sent: Monday, July 16, 2001 3:10 PM
  >   > To: 'eCos Discussion'
  >   > Subject: [ECOS] RTC format
  >   > 
  >   > 
  >   > Is there a standard format for RTCs?  I don't know what to 
  >   > write to the RTC 32-bit register to set it.  I came up with 
  >   > my own hh:mm:ss.xxx format for storage in a 32 bit 
  >   > register, but I wonder if it's compatible?  After all, I 
  >   > certainly hope it's not based on ms from some date because 
  >   > it would only store 49.xxx days then.
  >   > 
  >   > bit   | measurement
  >   > _________________
  >   > 27-23 | hours
  >   > 22-17 | minutes
  >   > 16-10 | seconds
  >   > 9-0   | milliseconds
  >   > 
  >   > 
  > 

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2001-07-16 14:55 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-07-16 14:09 [ECOS] RTC format Trenton D. Adams
2001-07-16 14:14 ` Trenton D. Adams
2001-07-16 14:55 Trenton D. Adams

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).