public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andy Hawkins <a.hawkins@cabletime.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problems with u-boot, PPChameleonEVB and MontaVista kernel
Date: Tue, 24 Feb 2004 15:45:44 -0000	[thread overview]
Message-ID: <001b01c3faed$44c266d0$333335bf@cabletime.com> (raw)
In-Reply-To: <20040224153407.6CF2DC0655@atlas.denx.de>

> 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?

Well, we've decided to use the MontaVista distribution / development
environment, and that integrates nicely with their kernel build tools.
There may well be features that are present in the MontaVista kernel
tree that we would like to use too (although I'd have to check the
details). I think the general feeling is that having one source for
all this is the best way to go (if we can get it to work).

> 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).

You're absolutely right, I don't understand exactly what I'm doing :).
No offence taken whatsoever. I've read through most of 'Understanding
the Linux Kernel', but unfortunately it only covers the early kernel
boot process for the i386 architecture. Is there any other reference
that can give more information for the PowerPC?

> 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/LinuxHangsAfterUncompressingKer
nel

I've followed the information in that FAQ. However, all it tells me to
do is match up the bd_info structures, and check clock information.

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

It just seems to make sense to try to keep everything (kernel, apps,
development etc.) under 'one roof' (i.e. MontaVista) if at all
possible.

I think whichever kernel tree we use, we're going to have to do some
porting either way, so I'd appreciate some guidance as to where in the
kernel I should be looking to resolve the problems we currently have
(as I might need the knowledge gained when we come to adding further
customisations later).

We *do* have a BDI 2000, but I think my ability to be able to debug
this problem is hindered by my limited knowledge of the kernel startup
code.

Any pointers on how to improve that knowledge (URLs, book and the
like), with specific reference to the PowerPC processor, would be much
appreciated.

Thanks to all who have replied thus far.

Andy

  reply	other threads:[~2004-02-24 15:45 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
2004-02-24 15:45   ` Andy Hawkins [this message]
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='001b01c3faed$44c266d0$333335bf@cabletime.com' \
    --to=a.hawkins@cabletime.com \
    --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