From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Date: Sun, 13 Feb 2005 10:22:58 +0200 Subject: [U-Boot-Users] i2c compiling and/or linking problem - solved (for the archive) In-Reply-To: <420CCAFE.3000004@smiths-aerospace.com> References: <20050210192313.8CB45C108D@atlas.denx.de> <420CC656.7000309@web.de> <420CCAFE.3000004@smiths-aerospace.com> Message-ID: <20050213082258.GB3025@nbase.co.il> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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.