linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: annamaya <annamaya@yahoo.com>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Booting Linux using a PlanetCore BootLoader
Date: Mon, 11 Oct 2004 10:33:44 -0700 (PDT)	[thread overview]
Message-ID: <20041011173344.62221.qmail@web53810.mail.yahoo.com> (raw)
In-Reply-To: <079593FC-1BA4-11D9-A165-003065F9B7DC@embeddededge.com>

Dan,
First let me thank you for still being around to
answer questions for people like me. You helped me out
a lot a few years ago when I was just starting to work
on all the embedded stuff. I am glad you are still
helping everyone else.

I will try the zImage trick but I just wanted to know
if the assumption here is that the kernel already
understands the EEPROM data format to construct
bd_info. Is that correct? If the kernel is unable to
get to this data, is there another way to pass this
info to the kernel?

Thanks much.

--- Dan Malek <dan@embeddededge.com> wrote:

> 
> On Oct 11, 2004, at 12:04 PM, annamaya wrote:
> 
> > I am trying to boot a linux kernel using a
> PlanetCore
> > BootLoader on an embedded planet board. I am used
> to
> > always using U-Boot for my Kernel booting needs. I
> am
> > not sure how to get this going on a PlanetCore
> boot
> > loader.
> 
> You need to build a zImage so you get the simple
> bootloader that will read the information from the
> EEPROM
> and format the board structure.
> 
> Load the zImage file as a binary.  It has a 64K ELF
> header
> on it, so you can either use 'dd' to strip that
> before the
> download or add 64K to the load address to use as
> the
> start address.  The start address is the first
> instruction of
> the image (or +64K if you didn't remove the ELF
> header).
> 
> 
> 	-- Dan
> 
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 

  reply	other threads:[~2004-10-11 17:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-11 16:04 Booting Linux using a PlanetCore BootLoader annamaya
2004-10-11 16:38 ` Dan Malek
2004-10-11 17:33   ` annamaya [this message]
2004-10-11 18:52     ` Dan Malek
2004-10-11 17:50   ` annamaya
2004-10-11 18:15     ` Tom Rini
2004-10-11 18:38       ` annamaya
2004-10-11 18:47         ` Tom Rini
2004-10-11 21:18           ` annamaya
2004-10-11 21:44             ` Tom Rini
2004-10-11 22:52               ` annamaya
2004-10-11 18:55     ` Dan Malek
     [not found] <20041012003339.B1EB92BDDA@ozlabs.org>
2004-10-12  1:12 ` Sam Song
2004-10-12 21:02   ` annamaya
2004-10-12 21:26     ` Dan Malek
2004-10-13 14:49       ` annamaya
2004-10-13 16:07         ` Dan Malek
2004-10-13 18:06           ` annamaya
2004-10-13 19:21             ` annamaya
2004-10-13 21:19               ` Dan Malek
2004-10-13 21:23                 ` annamaya
2004-10-13 22:47                   ` Dan Malek
2004-10-14 15:53                     ` annamaya
2004-10-14 16:45                       ` Dan Malek
2004-10-14 18:10                         ` annamaya
2004-10-14 20:54                           ` Wolfgang Denk
2004-10-16  0:16                           ` Sam Song

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=20041011173344.62221.qmail@web53810.mail.yahoo.com \
    --to=annamaya@yahoo.com \
    --cc=dan@embeddededge.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).