From mboxrd@z Thu Jan 1 00:00:00 1970 From: Frank Agius Subject: Re: No console output (omap-3.2 branch) Date: Wed, 25 Jan 2012 17:15:26 -0500 Message-ID: <4F207EFE.1010902@yahoo.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from lo.gmane.org ([80.91.229.12]:55873 "EHLO lo.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750891Ab2AYWPn (ORCPT ); Wed, 25 Jan 2012 17:15:43 -0500 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RqB81-0004bQ-WF for linux-omap@vger.kernel.org; Wed, 25 Jan 2012 23:15:42 +0100 Received: from static-50-52-145-66.lkvl.mn.frontiernet.net ([50.52.145.66]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 25 Jan 2012 23:15:41 +0100 Received: from ftagius by static-50-52-145-66.lkvl.mn.frontiernet.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 25 Jan 2012 23:15:41 +0100 In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: linux-omap@vger.kernel.org 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