From: Peter Asemann <peter.asemann@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] i2c compiling and/or linking problem
Date: Thu, 10 Feb 2005 18:21:42 +0100 [thread overview]
Message-ID: <420B9826.9080405@web.de> (raw)
In-Reply-To: <20050210170529.DDFD1C108D@atlas.denx.de>
>>So I just added an #include <i2c.h> in to my boards board.c, put #define
> Why would you need this?
No idea, just because others do include it for some reason.
>>CFG_HARD_I2C in the include-file and thought that'd be enough.
> Why do you want to use CFG_HARD_I2C? Soft-I2C is much easier.
I thought that CFG_HARD_I2C would do everything on its own - and there's
less to configure in the /include/configs/board.h file.
Why is the HARD I2c so much more difficult?
> Maybe there is no hardware I2C implementation for your processor?
I just assumed there was one for the MPC875, maybe that was premature.
> You only have to compare the board config files. No other changes are
> needed. Again, I recommend to use soft-i2c instead. There is zero
> advantages with hard-i2c, just a lot of trouble.
You're the expert, I'm convinced ;-)
Thanks a lot,
Peter Asemann
next prev parent reply other threads:[~2005-02-10 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 16:42 [U-Boot-Users] i2c compiling and/or linking problem Peter Asemann
2005-02-10 17:05 ` Wolfgang Denk
2005-02-10 17:21 ` Peter Asemann [this message]
2005-02-10 19:23 ` Wolfgang Denk
2005-02-11 14:51 ` [U-Boot-Users] i2c compiling and/or linking problem - solved (for the archive) Peter Asemann
2005-02-11 15:10 ` Jerry Van Baren
2005-02-11 17:33 ` Wolfgang Denk
2005-02-13 8:22 ` Gleb Natapov
2005-02-11 17:28 ` 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=420B9826.9080405@web.de \
--to=peter.asemann@web.de \
--cc=u-boot@lists.denx.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