From: Dirk Behme <dirk.behme@googlemail.com>
To: Martin Margraf <m_margraf@web.de>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Kernel 2.6.16 hangs after start booting with U-Boot 1.1.2
Date: Wed, 24 May 2006 16:35:56 +0200 [thread overview]
Message-ID: <44746F4C.60500@gmail.com> (raw)
In-Reply-To: <922740597@web.de>
Martin Margraf wrote:
> my problem is that after updating u-boot from 1.1.1 to 1.1.2 and after patching /arch/arm/boot/compressed/makefilfe and head-omap.S
> the kernel is hanging up at start. i use the latest kernel (2.6.16.18) and patched it with the 2.6.16-omap1 patch.
You don't tell us which board you use, which patches you
applied to makefile and head-omap.S and where kernel hangs.
Try to enable
Kernel hacking -> Kernel debugging -> Kernel low-level
debugging functions
for debugging.
Often made mistake are wrong parameters passed from u-boot
to kernel (e.g. board ID) after u-boot update.
Why do you update to u-boot 1.1.2 and not latest one (1.1.4)?
Cheers
Dirk
next prev parent reply other threads:[~2006-05-24 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 13:03 Kernel 2.6.16 hangs after start booting with U-Boot 1.1.2 Martin Margraf
2006-05-24 14:35 ` Dirk Behme [this message]
2006-05-26 22:08 ` Tony Lindgren
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=44746F4C.60500@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=m_margraf@web.de \
/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