Skip to contentSkip to conversation

Linux 2.6 on MPC5200. First port attempt ... Early problems ;(

DISCUSSION Sylvain Munaut 2 participants 2 messages Mar 5, 2004

lore
Share & tools
lore
#0 lore raw

Hello,

I'd like to run a 2.6 on a MPC5200 based board. Even if at first I'll only use a 2.4 in production, I figured that the sooner I start to test 2.6, the sooner I'll be able to use it with enough stability. So I started to tweak the 2.6.3 tree to make it boot on my LITE5200.

So, I've written/ported/copied some code for the console, the early serial debug, ..., added the MPC to cputable.c and modified the Kconfig/Makefile to build theses.
So far I don't seen anything on the serial console and apparently, the call the setup_common_caches ( in the cpu_setup_6xx.S ), never returns. But the code is an exact copy of the 2.4 version ...

The method I use to trace where the execution goes or not is through the leds connected to the GPIOs. From what I understood, the MBAR ( 0xf0000000 ) is always mapped so I can trace with MMU on or off.

Anyone could give me a clue ?

Sylvain Munaut

PS: I'm not an expert in PPC arch. However, I've done such a port ( 2.4 -> 2.6 ) for an ARM architecture, so I'm not completly new to this either ( even if ARM and PPC are little alike ... )

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

#1 lore raw

Kernel startup assumptions/requirements

I am new to Linux and am in the process of trying to get a kernel booted on a PPC board. What assumptions/requirements (if any) does the kernel have about any system state/setup prior to the execution of the kernel entry point?

Is it simply that the kernel is loaded and memory is accessible? MMU
on/off? Do any other peripherals (e.g 10ms timer) need to be initialized?

Thanks,
Stuart Yoder

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