From: Andre Puschmann <andre.puschmann@tu-ilmenau.de>
To: Steve Sakoman <sakoman@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Problem booting Overo Tide at 720MHz
Date: Wed, 28 Dec 2011 18:19:15 +0100 [thread overview]
Message-ID: <4EFB4F93.8010604@tu-ilmenau.de> (raw)
In-Reply-To: <CAGDS+nn7QUpcbbAxXdph_fr_k8Qir_eES811j3_UfX5AaN0=6Q@mail.gmail.com>
On 12/28/2011 06:09 PM, Steve Sakoman wrote:
> On Wed, Dec 28, 2011 at 7:26 AM, Andre Puschmann
> <andre.puschmann@tu-ilmenau.de> wrote:
>> Hi list,
>>
>> a couple of days ago I was posting a similar issue where Linux wouldn't
>> start after u-boot. I am trying to boot a recent kernel using Steve's
>> omap-3.2 branch on an Overo Tide based board.
>>
>> A recent checkout doesn't boot and hangs after u-boot hands over to the
>> kernel. After some digging I figured out that this has something to do
>> with the OPP settings for running at 720MHz.
>>
>> After commenting out omap3_opp_enable_720Mhz() in opp3xxx_data.c the
>> kernel boots fine.
>>
>> Does this work for all others?
>
> Seems to work fine for me.
>
> Give the binary here a try and let me know if it works for you:
>
> http://feeds.sakoman.com/feeds/yocto/images/omap3-multi/current/
>
> If it does then perhaps it is a defconfig issue. If not, then I need
> to dig up a Tide to try to reproduce.
>
> Steve
Nope, doesn't work either. The funny thing is that it works for the
omap3-pm branch which has the 720MHz thing included, too. So maybe the
workaround is just hiding something else?
Andre
next prev parent reply other threads:[~2011-12-28 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 15:26 Problem booting Overo Tide at 720MHz Andre Puschmann
2011-12-28 17:09 ` Steve Sakoman
2011-12-28 17:19 ` Andre Puschmann [this message]
2011-12-28 17:28 ` Steve Sakoman
2011-12-28 19:32 ` Andre Puschmann
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=4EFB4F93.8010604@tu-ilmenau.de \
--to=andre.puschmann@tu-ilmenau.de \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.