public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Chuck Meade <chuckmeade@mindspring.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problems with u-boot, PPChameleonEVB and MontaVista kernel
Date: Tue, 24 Feb 2004 12:18:14 -0500	[thread overview]
Message-ID: <IIEEICKJLNEPBBDJICNGMECGEMAA.chuckmeade@mindspring.com> (raw)
In-Reply-To: <001b01c3faed$44c266d0$333335bf@cabletime.com>

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

Hi again Andy,
At least this time I read your question more thoroughly :)

We are becoming off-topic for the U-Boot list -- if you want to take
this further, switch to the linuxppc list.

I can tell you for a start that you will need to customize your Linux
.config file (make menuconfig for example) for your particular target,
and you will also want to study the platform-specific code under
arch/ppc/platforms.  If your target is not currently supported, you
will need to create that support.  That means *at least* the files under 
arch/ppc/platforms, and the Makefile and Config.in changes needed
in the tree to support selection of the new platform and its features.

I encourage you to do a search of the entire Linux tree (not case 
sensitive) for a word like "walnut":

  find . -type f |xargs grep -i walnut

This will give you a feel for the places that platform-specifics
pop up.

Hope that helps,
Chuck

  parent reply	other threads:[~2004-02-24 17:18 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
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 [this message]
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=IIEEICKJLNEPBBDJICNGMECGEMAA.chuckmeade@mindspring.com \
    --to=chuckmeade@mindspring.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