linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Pokki <kalle.pokki@iki.fi>
To: Dan Malek <dan@embeddedalley.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: CPM2 early console
Date: Mon, 03 Oct 2005 09:04:15 +0200	[thread overview]
Message-ID: <4340D7EF.2040709@iki.fi> (raw)
In-Reply-To: <26a6f673ac9438729eccfe0c376c6b3d@embeddedalley.com>

Dan Malek wrote:

> What about just trying to boot the new kernel from PlanetCore boot rom?


I do use PlanetCore to boot the system. Basically the only funtionality 
in my own custom boot loader with this board is to carry the image of 
the Linux kernel, decompress, and launch it. I have disabled all the 
initialisation code since it was previously written for another board, 
and PlanetCore does all the initialisations anyway. I didn't care to 
erase PlanetCore from the flash just yet, since I can just as well 
develop the real initialisations later with the custom board.

PlanetCore itself is not usable for booting any other Linux kernel than 
the pre-installed one. It just allows me to launch some launcher of the 
Linux kernel... Probably it's the launcher that does the tricks to make 
Linux run correctly.

> Of course, if you are doing your own boot rom and have a board to 
> bring up,
> you should have invested in something like a BDI2000 long ago because 
> it will
> have paid for itself many times over by the time you are done :-)  It 
> would have
> also allowed you to debug this problem rather quickly.
>
You are right, this would be a lot easier with a good debugger. I just 
have delayed purchasing it since I wasn't previously sure if we'd use 
the PowerQUICC II family or not. I already have Lauterbach for 8xx, but 
the Linux community seems to prefer the BDI2000. Do you know if it fits 
better in Linux development? At least it seems to be a lot less 
expensive than a new Lautherbach license for the 82xx family.

  reply	other threads:[~2005-10-03  7:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22 16:02 CPM2 early console Rune Torgersen
2005-09-22 16:05 ` Kumar Gala
2005-09-23 10:55 ` Kalle Pokki
2005-09-27 14:11   ` Kalle Pokki
2005-09-27 16:39     ` Dan Malek
2005-09-27 20:35       ` Kalle Pokki
2005-09-27 20:48         ` Dan Malek
2005-09-28 10:20           ` Kalle Pokki
2005-09-29 12:24             ` Kalle Pokki
2005-09-29 12:50               ` Dan Malek
2005-09-30 13:22               ` Alex Zeffertt
2005-09-30 13:42                 ` Alex Zeffertt
2005-09-30 20:16                   ` Kalle Pokki
2005-09-30 13:58                 ` Dan Malek
2005-09-30 20:10                   ` Kalle Pokki
2005-09-30 20:28                     ` Dan Malek
2005-10-01  5:57                       ` Kalle Pokki
2005-10-01  8:24                         ` Roger Larsson
2005-10-02 16:59                         ` Dan Malek
2005-10-03  7:04                           ` Kalle Pokki [this message]
2005-10-04  8:13                             ` Kalle Pokki
2005-10-04  9:59                               ` Alex Zeffertt
2005-10-04 10:16                                 ` Kalle Pokki
2005-10-04 16:04                               ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2005-09-22 13:11 Kalle Pokki

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=4340D7EF.2040709@iki.fi \
    --to=kalle.pokki@iki.fi \
    --cc=dan@embeddedalley.com \
    --cc=linuxppc-embedded@ozlabs.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).