From: arend@broadcom.com (Arend van Spriel)
To: linux-arm-kernel@lists.infradead.org
Subject: Linux Kernel boot up stops after message "Uncompressing Linux....done, booting the kernel"
Date: Thu, 24 May 2012 15:13:15 +0200 [thread overview]
Message-ID: <4FBE33EB.3090709@broadcom.com> (raw)
In-Reply-To: <CACZ0kf9yHJOAVEBx4e5dc_eCRT5dScrZHzbkx3_7P2QkzaHChQ@mail.gmail.com>
On 05/24/2012 07:22 AM, K K wrote:
> Hi,
>
> We have a lpc-3180 based board and it is up and running fine with 2.6.10
> kernel version. We planned to port our board changes into 2.6.32 kernel
> version.
>
> As a part of this, we added the architecture dependent code (mach
> files) first. Then we changed some of the kernel upgradations.
>
> kernel build successfully. When we booting the board with the new 2.6.32
> kernel we are getting following messages and its stops.
I had a similar issue with a Pandaboard and I needed to patch u-boot:
diff --git a/include/configs/omap4_common.h b/include/configs/omap4_common.h
index d8ac8c0..89f9e89 100644
--- a/include/configs/omap4_common.h
+++ b/include/configs/omap4_common.h
@@ -36,6 +36,7 @@
#define CONFIG_OMAP44XX 1 /* which is a 44XX */
#define CONFIG_OMAP4430 1 /* which is in a 4430 */
#define CONFIG_ARCH_CPU_INIT
+#define CONFIG_SYS_DCACHE_OFF 1 /* not d-cache in u-boot */
/* Get CPU defs */
#include <asm/arch/cpu.h>
Gr. AvS
prev parent reply other threads:[~2012-05-24 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACZ0kf88Ac8hne9RtLObi624okPw8Nkiv7++Uw8npPLW108mhw@mail.gmail.com>
2012-05-24 5:22 ` Linux Kernel boot up stops after message "Uncompressing Linux....done, booting the kernel" K K
2012-05-24 10:32 ` Domenico Andreoli
2012-05-24 10:56 ` Baruch Siach
2012-05-25 12:50 ` K K
2012-05-24 13:13 ` Arend van Spriel [this message]
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=4FBE33EB.3090709@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).