All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org
Cc: Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: Strange behavior with I2C on Sequoia board
Date: Thu, 21 Aug 2008 11:51:40 +0200	[thread overview]
Message-ID: <200808211151.40499.sr@denx.de> (raw)
In-Reply-To: <20080820231828.3c22da08@lappy.seanm.ca>

On Thursday 21 August 2008, Sean MacLennan wrote:
> > That's all output from the wrapper, not the kernel.  And the kernel
> > config doesn't make a difference at all to the wrapper.  I wonder if
> > there is some weird size issue going on there or if whatever U-Boot
> > version you are using is doing odd things...
>
> Any chance something in the DTS could affect it? Maybe try commenting
> out the second IIC controller?

Yes, I2C is generally working and should make a difference in Linux kernel 
booting.

It seems that your bootwrapper is somehow not copying the correct MAC address 
to the device-tree. Not sure what's going wrong here. We usually don't use 
the bootwrapper but boot the uImage directly from U-Boot on all 4xx systems.

You might want to debug the bootwrapper code, if possible drop the bootwrapper 
and use the uImage with a newer, device-tree enabled U-Boot version.

Best regards,
Stefan

  reply	other threads:[~2008-08-21  9:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 20:55 Strange behavior with I2C on Sequoia board Steven A. Falco
2008-08-21  0:44 ` Josh Boyer
2008-08-21  3:18   ` Sean MacLennan
2008-08-21  9:51     ` Stefan Roese [this message]
2008-08-21 12:30       ` Valentine Barshak
2008-08-21 13:27         ` Steven A. Falco
2008-08-21 14:32           ` Stefan Roese
2008-08-21 14:33           ` Geert Uytterhoeven
2008-08-21 14:40             ` Stefan Roese
2008-08-21 18:45             ` Wolfgang Denk
2008-08-21 14:16         ` Stefan Roese
2008-08-21 18:45         ` 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=200808211151.40499.sr@denx.de \
    --to=sr@denx.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=smaclennan@pikatech.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.