From: Babarovic Ivica <ivica@asist-traffic.com>
To: egoforth@gmail.com, linuxppc-embedded@ozlabs.org
Subject: Re: I2C RTC recommendations?
Date: Tue, 15 Mar 2005 15:43:16 +0100 [thread overview]
Message-ID: <4236F484.9050301@asist-traffic.com> (raw)
In-Reply-To: <4235BD6A.5000004@gmail.com>
Ed Goforth wrote:
> I'm looking to add a RTC to a custom 440gx-based board. The board
> developer has indicated that they would prefer use an I2C device (vs.
> eg. something like the DS1743 that's on the reference board).
I got my board equipped with Epson's RX-8025 SA/NB RTC module.
I managed to get it working with a few hacks to a 8564 RTC driver
from Stefan Eletzhofer This RTC module is also from Epson.
So far everything works fine. I don't really know why board designers
decided for it but I suppose the main concern was price. :D
regards,
Ivica
prev parent reply other threads:[~2005-03-15 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 16:35 I2C RTC recommendations? Ed Goforth
2005-03-15 14:43 ` Babarovic Ivica [this message]
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=4236F484.9050301@asist-traffic.com \
--to=ivica@asist-traffic.com \
--cc=egoforth@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
/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 NNTP newsgroup(s).