Unfortunately, all the applications are running on 2.4 kernel. I can not just throw the 2.4 kernel. I took the some core specific code from ppc.bkbits.net, such as head_e500.S and mpc85xx_cds_common.c. I assume the image should work on the 8548 CDS board, or at least for the bootup. I shall able to have the serial port working in platform_init(). However , the code stops in the head_e500.S. This does not make any sense. Please correct me if I am wrong.
BTW, I am using the tool-chain gcc-3_4-e5000glibc-2.3.4-dp, which is from Freescale for the 8548 CDS BSP of 2.6 kernel. Any suggest or comment is welcome, I am struggling with this issue for almost one week...... :-( On 8/15/07, Becky Bruce <[EMAIL PROTECTED]> wrote: > > > On Aug 15, 2007, at 11:28 AM, Kumar Gala wrote: > > > > > On Aug 15, 2007, at 11:02 AM, Scott Wood wrote: > > > >> On Wed, Aug 15, 2007 at 09:57:59AM -0400, mike zheng wrote: > >>> Did you done similar work before? Current 2.6 code need many other > >>> files, I > >>> have following errors when I try to use the head_e500.S from 2.6 > >>> code: > >>> > >>> > >>> /kernel-> powerpc-linux-gnuspe-gcc -m32 -Wp,-MD,arch/ppc/ > >>> kernel/.entry.o.d > >>> -nostdinc -isystem /opt/mtwk/usr/local/gcc-3_4- > >>> e500-glibc-2.3.4-dp/powerpc-linux-gnuspe/lib/gcc/powerpc-linux- > >>> gnuspe/3.4.3/include > >>> -D__KERNEL__ -Iinclude -Iarch/ppc -D__ASSEMBLY__ -Iarch/ppc -Wa,- > >>> me500 -c > >>> -o arch/ppc/kernel/entry.o arch/ppc/kernel/entry.S > >>> arch/ppc/kernel/entry.S: Assembler messages: > >>> > >>> entry.S:819: Error: unsupported relocation against CSRR0 > >>> entry.S:820: Error: unsupported relocation against CSRR1 > >>> entry.S:888: Error: unsupported relocation against MCSRR0 > >>> entry.S:889: Error: unsupported relocation against MCSRR1 > >>> entry.S:909: Error: unsupported relocation against CSRR0 > >>> entry.S:911: Error: unsupported relocation against CSRR1 > >> > >> Try arch/powerpc; arch/ppc is deprecated. > > > > He's trying a 2.4 kernel. > > I think maybe he misunderstood Jon's advive to "use 2.6" as using > just some files from 2.6. I think the above is probably some strange > mix of 2.4 and 2.6, which, of course, won't work. > > Jon's real advice was "use 2.6", as in, the whole thing. > > -B > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-dev >
_______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev