On Sat, Sep 25, 2010 at 8:21 AM, Chen Dai <[email protected]> wrote:
> maybe it is related to u-boot
> because i also build an u-boot use the beagleboard config, the kernel can
> boot successfully
Well, that depends, when you built with the beagleboard u-boot did you
atleast change the mach # (devkit8000 is 2330):
diff --git a/board/ti/beagle/beagle.c b/board/ti/beagle/beagle.c
index 3b4c9e7..49a8d98 100644
--- a/board/ti/beagle/beagle.c
+++ b/board/ti/beagle/beagle.c
@@ -50,7 +50,7 @@ int board_init(void)
gpmc_init(); /* in SRAM or SDRAM, finish GPMC */
/* board id for Linux */
- gd->bd->bi_arch_number = MACH_TYPE_OMAP3_BEAGLE;
+ gd->bd->bi_arch_number = 2330;
/* boot param addr */
gd->bd->bi_boot_params = (OMAP34XX_SDRC_CS0 + 0x100);
Otherwise your board is booting up as a beagle board-omap3beagle.c...
I know they are clones, but they dont' use the same kernel board file
and those patches touch board-devkit8000.c..
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
