All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eran Mann <emann@mrv.com>
To: digitalRNA <horizonprits@yahoo.co.jp>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: u-boot-0.3.0 + Linux boot failed on walnut
Date: Wed, 21 May 2003 22:47:43 +0300	[thread overview]
Message-ID: <3ECBD7DF.2080609@mrv.com> (raw)
In-Reply-To: <3ECBB43B.2000601@yahoo.co.jp>


digitalRNA wrote:
> Hello,
>
> Now I am trying to boot Linux using u-boot-0.3.0 not openbios on walnut.
> But it failed.
> It looks failed around timer initialization on vmlinux.
> But in the case of openbios, the Linux can boot.
> Are there any information about this issue?
<snip>
Last time I checked the Walnut support code in linuxppc_2_4_devel and
linuxppc_2_5 assumed OpenBIOS board_info structure and not
U-Boot/PPCBoot board_info structure. The result is that the kernel took
the first 4 bytes of the Ethernet address passed from U-Boot as the
memory size, which ofcourse made the MM code quite unhappy later on ;-)

The brute-force solution is to replace the definition of the struct in
walnut.h (which is in arch/ppc/platforms/4xx in 2.5 and in
arch/ppc/platforms in 2.4_devel)

typedef struct board_info {
...
} bd_t;

with:
#include <asm/ppcboot.h>

The non-brute-force solution is of course to do it based on #ifdef
CONFIG_USE_PPCBOOT or something like that. Unfortunately this
configuration option does not exist in 2.5 .

--
Eran Mann
Senior Software Engineer
MRV International
Tel: 972-4-9936297
Fax: 972-4-9890430
www.mrv.com


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

      parent reply	other threads:[~2003-05-21 19:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-21 17:15 u-boot-0.3.0 + Linux boot failed on walnut digitalRNA
2003-05-21 19:46 ` Wolfgang Denk
2003-05-21 19:47 ` Eran Mann [this message]

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=3ECBD7DF.2080609@mrv.com \
    --to=emann@mrv.com \
    --cc=horizonprits@yahoo.co.jp \
    --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 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.