Re: linux-omap-2.6.35 on beagleboard based device hangs after booting the kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 4 Aug 2010 08:39:19 +0300
Tony Lindgren <tony@xxxxxxxxxxx> wrote:

> > I was using beagleboard_defconfig, which probably was insufficient, I should have used omap3_defconfig.
> 
> Hmm, sounds like there's something wrong with beagleboard_defconfig
> then. Care to enable CONFIG_DEBUG_LL=y and CONFIG_EARLY_PRINTK=y
> and add earlyprintk to kernel cmdline and see if you get any
> more info why it hangs?
> 
I have Beagle C2 with U-boot 2009.01-dirty and both v2.6.35 and l-o head
c287f2c5e0b80a272b9ee2032feef7366dcc1e64 boots ok with
omap3_beagle_defconfig.

Does you custom board have the same machine id than Beagle? You'll see
that also with earlyprintk if machine id from bootloader doesn't match
with board(s) support by the kernel.


-- 
Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux