All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valentine Barshak <vbarshak@ru.mvista.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Sequoia 440EPx patches not working
Date: Thu, 09 Aug 2007 20:21:20 +0400	[thread overview]
Message-ID: <46BB3F00.6060802@ru.mvista.com> (raw)
In-Reply-To: <20070809083443.2b2f5407@zod.rchland.ibm.com>

Josh Boyer wrote:
> On Thu, 09 Aug 2007 14:58:55 +0400
> Valentine Barshak <vbarshak@ru.mvista.com> wrote:
> 
>> David Gibson wrote:
>>> On Wed, Aug 08, 2007 at 01:45:10PM -0500, Jerone Young wrote:
>>>> Using the Sequoia (AMCC 440EPx) patches recently submitted to the
>>>> list I am unable to boot to fully boot a uImage built with these
>>>> patches under Uboot. It appears to hang in very early boot.
>>> I'm guessing this is an old version of u-boot, that's not device
>>> tree aware.  That would need a cuImage, not a uImage, and IIRC the
>>> posted patches didn't yet have cuboot support for Sequoia.
>>>
>> The patches do have cuImage support.
>> I have a Sequoia board with uBoot 1.1.6 and it boots cuImage fine.
> 
> Speaking of those patches, are you planning on rebasing them against
> the latest 4xx series I sent out soon?  That should have some cleanups
> that make adding sequoia support a bit easier.
> 
> josh

Yes, I do :)

  reply	other threads:[~2007-08-09 16:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 18:45 Sequoia 440EPx patches not working Jerone Young
2007-08-09  3:08 ` David Gibson
2007-08-09 10:58   ` Valentine Barshak
2007-08-09 13:34     ` Josh Boyer
2007-08-09 16:21       ` Valentine Barshak [this message]
2007-08-09 12:56 ` Vitaly Bordug
2007-08-09 13:42   ` Jerone Young
2007-08-09 14:37   ` Jerone Young
2007-08-09 16:33     ` Valentine Barshak
2007-08-13 21:04       ` Jerone Young

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=46BB3F00.6060802@ru.mvista.com \
    --to=vbarshak@ru.mvista.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    /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.