public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Trenton D. Adams" <tadams@extremeeng.com>
To: "'Trenton D. Adams'" <tadams@extremeeng.com>,
	"'eCos Discussion'" <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] RTC format
Date: Mon, 16 Jul 2001 14:55:00 -0000	[thread overview]
Message-ID: <000901c10e42$0ccac410$090110ac@TRENT> (raw)

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
  >   > 
  >   > 
  > 

             reply	other threads:[~2001-07-16 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16 14:55 Trenton D. Adams [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-16 14:09 Trenton D. Adams
2001-07-16 14:14 ` Trenton D. Adams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000901c10e42$0ccac410$090110ac@TRENT' \
    --to=tadams@extremeeng.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).