Compiling Linux Kernel for ML403

Magnus Hjorth mh at omnisys.se
Sat Feb 24 23:38:11 EST 2007


Hi Mohammad,

The files that are in generated in the BSP are for an older mvista kernel (based on 2.6.14 I think) and some things have changed since then. In particular some tables in virtex.c and xilinx_ml403.c are different. It's probably easier to fix these files manually than to copy the files from the BSP. 

You should rename the xparameters_ml40x.h in the BSP to xparameters_ml403.h. You may also need to add some #defines for constants that have changed names, which you will discover when you try to compile the kernel. 

You need to manually edit Kconfig files to get menuconfig entries, and you will need to edit some Makefiles to get it all to be compiled in. It could be easier in mvista, I don't know... Good luck!

Best regards,
Magnus

On Sat, 24 Feb 2007 09:44:33 +0000
Mohammad Sadegh Sadri <mamsadegh at hotmail.com> wrote:

> 
> Hi all,
> 
> Again , I have some questions:
> 
> I downloaded the linux kernel from both of source.mvista.com ( 2.6.19 I think ) and kernel.org ( 2.6.20 ) , and I did the following tests on both of them:
> 
> 1- Using EDK 8.2.02 , generated my base system for ml403. EDK generated BSP files. 
> 2- I copied the linux-2.6.20.tar.bz2 into proper location in eldk directory and extracted there, Then I copied all of the BSP files into the root folder of my kernel source.
> 3- Editted the Makefile and set the ARCH and CROSS_COMPILE variables , also I set all of the env variables needed by edk. 
> 
> 4- ( First Question ) looking the BSP files generated by EDK I see that /arch/ppc/platforms/4xx/xparameters contains two files: xparameteres.h and xparameters_ml40x.h 
> However when I look at the same folder in kernel source tree I see that the file name is different, it is xparameters_ml403.h 
> Is this OK? I think that I should rename the file?
> 
> 5- ( Second Question ) Although I have copied the BSP files into the my kernel source tree completely, nothing changes in the menuconfig. I mean the menuconfig ( menus and configs ) is the same as before, for example  , no special option is added for gigabit ethernet support ( hard temac )
> Is this ok? I expected to see some changes in menuconfig when I copied the files into kernel source. 
> 
> 6- ( Third Question ) Now, I do the needed primary configurations and then I type : make, to begin the build process. Obviously, It generates some error messages, Is this  kind of behaviour natural? I was not expecting to see syntax errors in kernel source tree ? ( Of course, when I build the kernel without Xilinx BSP every thing is OK )
> 
> ( The above descriptions are true for both of mvista and kernel.org, )
> 
> thanks
> 
> 
> 
> _________________________________________________________________
> Explore the seven wonders of the world
> http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded at ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded


-- 

Magnus Hjorth, M.Sc.
Omnisys Instruments AB
Gruvgatan 8
SE-421 30  Västra Frölunda, SWEDEN
Phone: +46 31 734 34 09
Fax: +46 31 734 34 29
http://www.omnisys.se 



More information about the Linuxppc-embedded mailing list