linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Matthew S. McClintock" <mattsm@arlut.utexas.edu>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MPC8245 and PCF8563 RTC
Date: 25 Jul 2003 09:24:47 -0500	[thread overview]
Message-ID: <1059143087.4969.21.camel@triffo.arlut.utexas.edu> (raw)
In-Reply-To: <20030724222654.7B845C602D@atlas.denx.de>


Do any of the boards you mentioned use the same i2c-adap driver that I
mentioned I was using for my board? Is there a better i2c-adap driver
for an MPC8245 board? I think the i2c driver for my board is the
culprit, not the driver for the real time clock. As always all help is
appreciated.

Thanks,
Matthew

On Thu, 2003-07-24 at 17:26, Wolfgang Denk wrote:
> Dear Matthew,
>
> in message <1059084423.4969.11.camel@triffo.arlut.utexas.edu> you wrote:
> >
> > Has anyone had any success using an MPC8245 and a Philips PCF8563 real
> > time clock in linux? Everything works in U-Boot but I can not get
> > everything working in linux.
>
> Not with a MPC8245, but with MPC8240 (on CU824  board),  MPC8250  (on
> PM825 board), and MPC8260 CPUs (on PM826 and CPU86 boards).
>
> > Obviously it has a transfer error, but I am curious if anyone has any
> > experiences with the same situation. Anyone have any ideas?
>
> Works fine here.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
> I read part of it all the way through.
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-07-25 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 22:07 MPC8245 and PCF8563 RTC Matthew S. McClintock
2003-07-24 22:26 ` Wolfgang Denk
2003-07-25 14:24   ` Matthew S. McClintock [this message]
2003-07-25 16:15     ` Wolfgang Denk

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=1059143087.4969.21.camel@triffo.arlut.utexas.edu \
    --to=mattsm@arlut.utexas.edu \
    --cc=linuxppc-embedded@lists.linuxppc.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).