linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Brian Hawley <bhawley@luminex.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Ebony Board, PPC440GP and NFS panics
Date: Wed, 19 May 2004 21:54:00 +0200	[thread overview]
Message-ID: <20040519195405.98971C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 19 May 2004 10:16:29 PDT." <4.2.2.20040519101456.0509d340@bhawley.mailhost.luminex.com>


In message <4.2.2.20040519101456.0509d340@bhawley.mailhost.luminex.com> you wrote:
>
> Is there something special that must be done for the kernel to be
> configured for use
> with u-boot?  A kernel config option, perhaps?

See the README file in the U-Boot source tree.  No,  this  is  not  a
kernel config option for most boards.

> I double checked the include/asm-ppc/u-boot.h in u-boot against
> include/asm-ppc/ppcboot.h in linux...and
> did find a section with a #define for CONFIG_405, but not 440.  We'll see
> if that makes a difference.

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?

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Of all the things I've lost, I miss my mind the most.

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

  reply	other threads:[~2004-05-19 19:54 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 [this message]
2004-05-19 19:36             ` Brian Hawley
2004-05-19 21:04               ` Eugene Surovegin
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=20040519195405.98971C109F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=bhawley@luminex.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 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).