On 12/10/2011 8:55 AM, Andre Puschmann wrote:
Hi list, Steve, I am trying to boot a kernel I built (using omap2plus_defconfig) based on Steve's omap-3.2 branch without much success. I don't get any console output after Uboot finished uncompressing the kernel. Is there anything I need to configure? The kernel image based on Tony's tree boots fine on the same hardware (Gumstix Overo Tide) (despite having MMC issues as mentioned earlier).
I ran into the same problem you described. Steve's tree has some patches that are not in mainline 3.2. I tracked the hang down to one of those patches that added support for 720Mhz capable hardware. The kernel reads the status register and determines that the CPU can support 720Mhz (omap3_check_features). From what I can tell, the check is done correctly (variable status in omap3_check_features is set to 0x08, which looks like the right bit for 720Mhz support). Since the kernel thinks that 720Mhz is supported, it calls omap3_opp_enable_720Mhz (file opp3xx_data.c). The kernel dies silently when it calls the opp enable for 720Mhz, at or near line 178:
176 pdev = &oh_mpu->od->pdev; 177 178 r = opp_enable(&pdev->dev, 720000000); That's as far as I can take the debug. I'm going to disable the check for 720Mhz in my local tree until this can get sorted out. frank -- 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
