Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: linux-omap@vger.kernel.org
Cc: paul@pwsan.com
Subject: OMAP2 not booting in 2.6.27-rc9?
Date: Thu, 9 Oct 2008 10:32:58 +0300	[thread overview]
Message-ID: <20081009103258.cbace620.jarkko.nikula@nokia.com> (raw)

Hi

At least N810 hangs somewhere executing local_flush_tlb_all() in
omap_map_sram. Last printk is before that call.

diff --git a/arch/arm/plat-omap/sram.c b/arch/arm/plat-omap/sram.c
index 853048d..5ddf417 100644
--- a/arch/arm/plat-omap/sram.c
+++ b/arch/arm/plat-omap/sram.c
@@ -215,8 +215,11 @@ void __init omap_map_sram(void)
 	 * mdesc->map_io(), but since we're called from map_io(), we
 	 * must do it here.
 	 */
+printk("%s @ %d\n", __func__, __LINE__);
 	local_flush_tlb_all();
+printk("%s @ %d\n", __func__, __LINE__);
 	flush_cache_all();
+printk("%s @ %d\n", __func__, __LINE__);
 
 	/*
 	 * Looks like we need to preserve some bootloader code at the


Reverting Paul's commit below doesn't help.

commit 61db7fb1c78c32b6abdc5c7965981de332aeaa5b
Author: Paul Walmsley <paul@pwsan.com>
Date:   Tue Aug 12 00:04:15 2008 +0100

    [ARM] 5192/1: ARM TLB: add v7wbi_{possible,always}_flags to
{possible,always


However Beagle is still booting fine with my current head

commit 5b99e69f31fa575e53483e1f90c3a88939ca0b95
Merge: f9ceca7... 4330ed8...
Author: Tony Lindgren <tony@atomide.com>
Date:   Tue Oct 7 14:27:17 2008 +0300

    Merge current mainline tree into linux-omap tree
    
    Merge branches 'master' and 'linus'


Jarkko

             reply	other threads:[~2008-10-09  7:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09  7:32 Jarkko Nikula [this message]
2008-10-09 11:58 ` OMAP2 not booting in 2.6.27-rc9? Paul Walmsley
2008-10-09 13:37 ` Paul Walmsley

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=20081009103258.cbace620.jarkko.nikula@nokia.com \
    --to=jarkko.nikula@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox