Am 25.03.2011 08:53, schrieb Belisko Marek: > On Fri, Mar 25, 2011 at 8:13 AM, Jarkko Nikula <[email protected]> wrote: >> On Thu, 24 Mar 2011 12:00:30 -0700 >> Tony Lindgren <[email protected]> wrote: >> >>> * Belisko Marek <[email protected]> [110324 08:18]: >>>> On Thu, Mar 24, 2011 at 4:18 PM, Tony Lindgren <[email protected]> wrote: >>>> >>>>> * Belisko Marek <[email protected]> [110324 02:50]: >>>>>> Hi, >>>>>> >>>>>> Try to run 2.6.38 on my sbc8100 >>>>>> (use mach-type for devkit8000 because boards are similar) board but >>>>>> when u-boot load it to ram I see just: >> ... >>>>> Can you enable DEBUG_LL and EARLY_PRINTK in your .config >>>>> and add earlyprintk to your cmdline? Then you should see >>>>> what goes wrong. >>>>> >>>> Forgot to mention. I already test this options but result is same like I >>>> report in >>>> first email. >>> >>> Maybe add some printk statements to start_kernel function in >>> init/main.c and see if you get any output? >>> >> For earlyprintk worth to check also >> arch/arm/plat-omap/include/plat/uncompress.h that there is entry for >> sbc8100 (double check with devkit8000 as there is entry for it and if >> you are re-using the mach-type). > Thanks for hint. It was missing there so I add line: > DEBUG_LL_OMAP3(3, devkit8000); (I'm convince linux to use mach-type > for devkit8000) > But still same result. > Bytes transferred = 2898680 (2c3af8 hex) > ## Booting kernel from Legacy Image at 80300000 ... > Image Name: Linux-2.6.37-00001-g88870c9-dirt > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 2898616 Bytes = 2.8 MB > Load Address: 80008000 > Entry Point: 80008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > > Anybody with devkit8000 have success to run 2.6.37 kernel on board? >> >> -- >> Jarkko >> > > regards, > > marek >
Hello Marek, yes, it is running. But your mach-type is wrong. Thats not the mach-type from devkit8000, it is spark. What version of u-boot are you running? Thomas -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
