From: Tony Lindgren <tony@atomide.com>
To: Anand Gadiyar <gadiyar@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: linux-next - multi-omap image fails to boot on omap3/4
Date: Tue, 19 Oct 2010 11:21:50 -0700 [thread overview]
Message-ID: <20101019182149.GC3038@atomide.com> (raw)
In-Reply-To: <4CBDAFFF.2030409@ti.com>
* Anand Gadiyar <gadiyar@ti.com> [101019 07:41]:
> Hi all,
>
> linux-next, as of 20101019, built with the omap2plus_defconfig fails
> to boot on omap3 and omap4. (I've disabled CONFIG_ARCH_OMAP2 or
> CONFIG_SWP_EMULATE to get the image to build). Building with only
> ARCH_OMAP3 allows the resultant image to boot up on OMAP3. Likewise,
> an image built with only ARCH_OMAP4 boots up on OMAP4 boards.
>
> earlyprintk does not provide any additional prints after
> "Uncompressing Linux... done, booting the kernel."
>
> Any ideas where to look?
Hmm I did a quick test merge of linux-omap master and rmk/devel
branches and that boots just fine.
So it's probably something that already got fixed in rmk/devel
but is not yet in next, or something that came from elsewhere,
or something that we have in omap-testing branch that's not in
for-next for some reason.
Regards,
Tony
next prev parent reply other threads:[~2010-10-19 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 14:49 linux-next - multi-omap image fails to boot on omap3/4 Anand Gadiyar
2010-10-19 18:21 ` Tony Lindgren [this message]
2010-10-19 18:35 ` Gadiyar, Anand
2010-10-19 22:57 ` Tony Lindgren
2010-10-19 23:32 ` Tony Lindgren
2010-10-19 23:46 ` Gadiyar, Anand
2010-10-20 6:30 ` Gadiyar, Anand
2010-10-21 16:15 ` Tony Lindgren
2010-10-22 14:08 ` Anand Gadiyar
2010-10-22 18:52 ` Tony Lindgren
2010-10-22 20:15 ` Anand Gadiyar
2010-10-22 21:38 ` 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=20101019182149.GC3038@atomide.com \
--to=tony@atomide.com \
--cc=gadiyar@ti.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 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.