On Thu, May 10, 2001 at 11:08:21AM +0800, machael thailer wrote: > > > 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?
You're doing this all wrong. There have been a bunch of good examples of ports to non-CHRP/PReP/Pmac 6xx/7xx/74xx hardware in the linuxppc_2_5 tree for a while now. Most of them have just been moved into the new linuxppc_2_4_devel tree. See the K2, MVME5100, MCPN765, PCore, PrPMC750, F1, etc. ports for details on how to quickly and easily do a port to a custom board. > 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? Yes. -- Matt Porter MontaVista Software, Inc. mporter at mvista.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
