From: Wolfgang Denk <wd@denx.de>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: I2C RTC causes boot delay...
Date: Tue, 08 Apr 2003 14:57:21 +0200 [thread overview]
Message-ID: <20030408125726.80D52C5877@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 08 Apr 2003 14:20:40 +0200." <3E92BE98.4090907@imc-berlin.de>
In message <3E92BE98.4090907@imc-berlin.de> you wrote:
>
> Yeah. I know. I should put into PPCBoot/U-Boot.
It's arelady there.
> But in the docs it says it's only for SOFT_I2C aka bitbang!
Right, because you cannot toogle the pins at your liking with the
CPM's I2C controller.
> a) can I toggle the pins using GPIO and still use HARD_I2C? or
Yes, you can. But this has not been implemented yet. And if you do,
you will find you have copied 90% of the soft_i2c driver so why not
use this from the beginning? Using HARD_I2C has _zero_ advantage for
U-Boot.
> b) can I use SOFT_I2C in PPCBoot and CPM I2C (8xx-algo) under linux?
Yes, you can.
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
THIS IS A 100% MATTER PRODUCT: In the Unlikely Event That This
Merchandise Should Contact Antimatter in Any Form, a Catastrophic
Explosion Will Result.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-04-08 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 10:28 I2C RTC causes boot delay Steven Scholz
2003-04-08 10:52 ` Steven Scholz
2003-04-08 12:01 ` Joakim Tjernlund
2003-04-08 12:20 ` Steven Scholz
2003-04-08 12:36 ` Joakim Tjernlund
2003-04-08 12:57 ` Wolfgang Denk [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=20030408125726.80D52C5877@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=steven.scholz@imc-berlin.de \
/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).