linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Brian Hawley <bhawley@luminex.com>
Cc: Wolfgang Denk <wd@denx.de>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Ebony Board, PPC440GP and NFS panics
Date: Wed, 19 May 2004 14:04:38 -0700	[thread overview]
Message-ID: <20040519210438.GA13351@gate.ebshome.net> (raw)
In-Reply-To: <4.2.2.20040519123513.05074da0@bhawley.mailhost.luminex.com>


On Wed, May 19, 2004 at 12:36:50PM -0700, Brian Hawley wrote:
>
> At 09:54 PM 5/19/04 +0200, Wolfgang Denk wrote:
>
>
> >The question is: does your "arch/ppc/platforms/ebony.h" include
> ><asm/ppcboot.h> or not, i. e. does it use the U-Boot definitions at
> >all?
>
> There is no ebony.h in arch/ppc/platforms...the board isn't listed there at
> all, neither
> is the walnut [ 405 ], but I've seen numerous people discuss the fact that
> they have
> the ebony board working with this (linux-2.5-ocp from bk) working.

It's arch/ppc/platforms/4xx/ebony.[ch]

And no, ebony.[ch] doesn't support u-boot. So it cannot work with u-boot if you
didn't change ebony.[ch].

You cannot just substitute boot loader without changing board support in Linux
kernel and expect it to work.

I can only suggest the same thing I told you before, get Ebony running with
standard IBM boot loader (OpenBIOS), study how Linux kernel interact with _this_
bootloader, study how u-boot differs from IBM OpenBIOS and only after having
full understanding how things work, try to port Ebony to using u-boot.

Eugene.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-05-19 21:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18  1:49 ELDK help Jack Liu
2004-05-18  7:31 ` Wolfgang Denk
2004-05-18 16:32 ` Ebony Board, PPC440GP and NFS panics Brian Hawley
2004-05-19  7:23   ` Gerhard Jaeger
2004-05-19 16:13     ` Brian Hawley
2004-05-19 17:37       ` Mark Chambers
2004-05-19 17:09         ` Brian Hawley
2004-05-19 17:59       ` Wolfgang Denk
2004-05-19 17:16         ` Brian Hawley
2004-05-19 19:54           ` Wolfgang Denk
2004-05-19 19:36             ` Brian Hawley
2004-05-19 21:04               ` Eugene Surovegin [this message]
2004-05-19 20:24                 ` Brian Hawley
2004-05-19 21:19                   ` Eugene Surovegin
2004-05-19 20:52                     ` Brian Hawley
2004-05-19 22:11                       ` Eugene Surovegin
2004-05-19 21:27                         ` Brian Hawley
2004-05-19 21:34                         ` Brian Hawley
2004-05-19 22:44                           ` Eugene Surovegin
2004-05-19 22:19                             ` Ebony Board, PPC440GP and NFS time out Brian Hawley
2004-05-19 23:42                               ` Eugene Surovegin
2004-05-19 23:09                                 ` Brian Hawley
2004-05-20  0:19                                 ` Eugene Surovegin
2004-05-19 23:40                                   ` Brian Hawley
2004-05-19 20:01             ` Ebony Board, PPC440GP and NFS panics Brian Hawley
     [not found]             ` <Your message of "Wed, 19 May 2004 10:16:29 PDT." <4.2.2.20040519101456.0509d340@bhawley.mailhost.luminex.com>
     [not found]               ` <4.2.2.20040519123513.05074da0@bhawley.mailhost.luminex.com >
2004-05-19 20:14                 ` Ebony Board, PPC440GP and Ramdisk Brian Hawley

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=20040519210438.GA13351@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=bhawley@luminex.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wd@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;
as well as URLs for NNTP newsgroup(s).