linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "machael thailer" <dony.he@huawei.com>
To: "Dan Malek" <dan@mvista.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Uncompress Ok, but cannot run linux kernel...
Date: Thu, 10 May 2001 11:08:21 +0800	[thread overview]
Message-ID: <000901c0d8fe$78abed40$8021690a@huawei.com> (raw)
In-Reply-To: 3AF6F323.7944F695@mvista.com


> machael thailer wrote:
> > ..... But I met
> > some urgent problems ...
> >     I modified the bootloader codes according to arch/ppc/mbxboot/head.S
>
> For starters, you shouldn't be using this "boot loader" for a 750.....
> How did you configure a kernel to get there in the first place?
> A 750 should be a CHRP (or PReP, if you have to.....), which will
> direct you to a working "chrpboot" boot loader.

If I use  "chrpboot " bootloader, I have to provide many functions in my
boot codes according to CHRP specifications:

1  "prom"(promptr) functions which can provide with "/chosen" ,"claim" and
"getprop" services etc in arch/ppc/chrpboot/start.c and in
arch/ppc/kernel/prom.c .
2  device-trees for my custom board.

Are these functions all necessary for booting the linux kernel?


And do I have to  modify arch/ppc/mm/init.c=>MMU_init() and
arch/ppc/kernel/setup.c=>identify_machines() to suit my cases?
I notice that in identify_machines(), there are many types initializations
functions such as pmac_init(),prep_init(),chrp_init(),apus_init(),
oak_init(),m8xx_init(),m8260_init(). Do I have to provide my own ***_init()
functions?


Thank you  very much.

machael


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-05-10  3:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-06  1:01 Uncompress Ok, but cannot run linux kernel machael thailer
2001-05-07 19:10 ` Dan Malek
2001-05-08  1:36   ` machael thailer
2001-05-10  3:08   ` machael thailer [this message]
2001-05-10 10:45     ` Matt Porter
2001-05-08  0:58 ` Michael Habermann
2001-05-08  1:16   ` Dan Malek
2001-05-08  8:02     ` Michael Habermann
2001-05-08  8:06       ` machael thailer
2001-05-08  8:43         ` Wolfgang Denk
2001-05-08 10:06           ` machael thailer
  -- strict thread matches above, loose matches on Subject: below --
2001-05-08 10:43 Zehetbauer Thomas
2001-05-08 11:51 ` machael thailer
     [not found] <439B3F1E9095D41193DE00D0B74FF30601CE7900@xpr01.prd.hp.com>
2001-05-08 13:50 ` Freddy Lugo
2001-05-08 15:21   ` Wolfgang Denk
2001-05-08 21:21     ` Freddy Lugo
2001-05-10  3:40 machael thailer
2001-05-10  4:16 ` Paul White

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='000901c0d8fe$78abed40$8021690a@huawei.com' \
    --to=dony.he@huawei.com \
    --cc=dan@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).