From: Gleb Natapov <gleb@nbase.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] i2c compiling and/or linking problem - solved (for the archive)
Date: Sun, 13 Feb 2005 10:22:58 +0200 [thread overview]
Message-ID: <20050213082258.GB3025@nbase.co.il> (raw)
In-Reply-To: <420CCAFE.3000004@smiths-aerospace.com>
On Fri, Feb 11, 2005 at 10:10:54AM -0500, Jerry Van Baren wrote:
> >Okay, the HARD code is twice as long and looks more complicated, but
> >this could - theoretically - also be the fault of the coder, not the
> >hardware.
>
> We're all above average here ;-). Seriously, there isn't much
> inefficient code in u-boot. About the only thing I can think of is the
> 8245 I2C code (which is hardware only)... that is an ugly glue-in of
> some example Mot code so we can Blame Someone Else[tm].
>
8245 no longer use Motorola code for i2c. So if you want to blame
someone, blame me :)
--
Gleb.
next prev parent reply other threads:[~2005-02-13 8:22 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
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 [this message]
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=20050213082258.GB3025@nbase.co.il \
--to=gleb@nbase.co.il \
--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