From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] i2c compiling and/or linking problem
Date: Thu, 10 Feb 2005 18:05:24 +0100 [thread overview]
Message-ID: <20050210170529.DDFD1C108D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 10 Feb 2005 17:42:38 +0100." <420B8EFE.7010301@web.de>
In message <420B8EFE.7010301@web.de> you wrote:
> Well, I wanted to compile u-boot with i2c support.
For which board? Which architecture?
> So I just added an #include <i2c.h> in to my boards board.c, put #define
Why would you need this?
> 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.
> Well... apparently that's not enough as compiling (make distclean done
> before) stops in the linking process with a lot of complaints like this:
...
> undefined reference to `i2c_read'
Maybe there is no hardware I2C implementation for your processor?
> So... any suggestions where to add some references so it find all the
> stuff? I tried to figure out what other boards that use i2c do, but
> couldn't find any hints that I missed some Makefile or config, got lost
> in the build-system.
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.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A penny saved is a penny to squander.
- Ambrose Bierce
next prev parent reply other threads:[~2005-02-10 17:05 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 [this message]
2005-02-10 17:21 ` Peter Asemann
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=20050210170529.DDFD1C108D@atlas.denx.de \
--to=wd@denx.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