linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Jacky Lam" <jackylam@astri.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Walnut boot problem solved
Date: Tue, 07 Oct 2003 00:40:17 +0200	[thread overview]
Message-ID: <20031006224023.069E7C59E4@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 06 Oct 2003 11:06:14 +0800." <009a01c38bb6$ceb84f40$2803050a@JackyLam>


Hi Jacky,

in message <009a01c38bb6$ceb84f40$2803050a@JackyLam> you wrote:
>
>     I have figured out why my kernel hanged while booting on Walnut
> platform. It is because the structure of board_info is different between
> u-boot-0.4.8 and linuxppc-2.4-devel. After syncing the structure, I can boot

Does the fact that this is a FAQ tell you something?

> up to where the kernel tries to mount the filesystem. Attached is a patch
> for the fix.

This patch is not really useful. Instead of redefining the  structure
yourself you should simply #include <asm/ppcboot.h>.

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
By the way, ALL software projects are done by iterative  prototyping.
Some companies call their prototypes "releases", that's all.

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

  reply	other threads:[~2003-10-06 22:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06  3:06 Walnut boot problem solved Jacky Lam
2003-10-06 22:40 ` Wolfgang Denk [this message]
2003-10-06 22:45   ` Jacky Lam
2003-10-07  7:39     ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2003-10-06  7:37 Jacky Lam

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=20031006224023.069E7C59E4@atlas.denx.de \
    --to=wd@denx.de \
    --cc=jackylam@astri.org \
    --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).