public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Agius <ftagius@yahoo.com>
To: linux-omap@vger.kernel.org
Subject: Re: No console output (omap-3.2 branch)
Date: Wed, 25 Jan 2012 17:15:26 -0500	[thread overview]
Message-ID: <4F207EFE.1010902@yahoo.com> (raw)
In-Reply-To: <jbvod7$rj2$1@dough.gmane.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


  reply	other threads:[~2012-01-25 22:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-10 13:55 No console output (omap-3.2 branch) Andre Puschmann
2012-01-25 22:15 ` Frank Agius [this message]
2012-01-26 10:13   ` Andre Puschmann
2012-01-26 10:27     ` Belisko Marek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F207EFE.1010902@yahoo.com \
    --to=ftagius@yahoo.com \
    --cc=linux-omap@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox