public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problems with u-boot, PPChameleonEVB and MontaVista kernel
Date: Tue, 24 Feb 2004 16:34:02 +0100	[thread overview]
Message-ID: <20040224153407.6CF2DC0655@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 24 Feb 2004 10:45:27 GMT." <000b01c3fac3$50750980$333335bf@cabletime.com>

In message <000b01c3fac3$50750980$333335bf@cabletime.com> you wrote:
> 
> I can successfully compile u-boot 1.0.0-pre and the kernel that came
> with the board (2.4.20 from the eldk), and boot the board
> successfully.
> 
> However, when I try to compile the MontaVista kernel, the board will
> not boot. Their kernel doesn't directly support the PPChameleonEVB, so

Is there any special reason to use their kernel? What does it contain
that you cannot find in DAVE's / our tested and working kernel tree?

> I'm using the one for the IBM 405EP eval (which the PPChameleon
> appears to be very similar to). I'm 'manually' running make pImage to

You have to accept the fact that "similar" is not  good  enough.  You
must  use  a  kernel  which  has  been proted to the _exact_ matching
board, or you will run into problems sooner or later -  at  least  if
you  don't  understand EXACTLY what you are doing (which seems not to
be the case - no offence meant).

> I've been in touch with MontaVista, and they suggest re-building
> u-boot, but changing the definition of the bd_info struction (in

Of course. You shall break compatibility to the  rest  of  the  world
just to make their kernel work. What a nonsense.

> I do have access to a BDI2000, that I've used to break into a running
> kernel (at start_here), but can't get it to break when I use the
> MontaVista kernel. From this, I assume that it's failing somewhere
> very early in the linux boot process.
> 
> Can anyone offer any advice?

Your question is a FAQ:
http://www.denx.de/twiki/bin/view/DULG/LinuxHangsAfterUncompressingKernel


What I cannot understand is why you are wasting your time (and  ours)
if you have a working kernel which you can use.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
"What is wanted is not the will to believe, but the will to find out,
which is the exact opposite." - Bertrand Russell, _Sceptical_Essays_,
1928

  parent reply	other threads:[~2004-02-24 15:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 10:45 [U-Boot-Users] Problems with u-boot, PPChameleonEVB and MontaVista kernel Andy Hawkins
2004-02-24 14:44 ` Chuck Meade
2004-02-24 14:46   ` Andy Hawkins
2004-02-24 15:22     ` Marius Groeger
2004-02-24 15:27       ` Andy Hawkins
2004-02-24 15:32       ` [U-Boot-Users] Problems with u-boot, PPChameleonEVB and MontaVistakernel Chuck Meade
2004-02-24 15:35     ` [U-Boot-Users] Problems with u-boot, PPChameleonEVB and MontaVista kernel Wolfgang Denk
2004-02-24 15:35   ` Wolfgang Denk
2004-02-24 15:43     ` Chuck Meade
2004-02-24 15:34 ` Wolfgang Denk [this message]
2004-02-24 15:45   ` Andy Hawkins
2004-02-24 16:09     ` Wolfgang Denk
2004-02-24 16:16       ` Andy Hawkins
2004-02-24 17:32         ` Wolfgang Denk
2004-02-24 17:18     ` Chuck Meade
2004-02-24 17:22       ` Andy Hawkins

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=20040224153407.6CF2DC0655@atlas.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.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