Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	Tony Lindgren <tony@atomide.com>,
	Nicolas Pitre <nico@fluxnic.net>,
	arm@kernel.org
Subject: Re: Failure to boot...
Date: Wed, 30 Jan 2013 19:02:03 -0800	[thread overview]
Message-ID: <20130131030203.GA8374@quad.lixom.net> (raw)
In-Reply-To: <20130131014912.GM2637@n2100.arm.linux.org.uk>

On Thu, Jan 31, 2013 at 01:49:12AM +0000, Russell King - ARM Linux wrote:
> Having spent today sorting out the Realview EB boot, the last thing
> I expected to find was that both my OMAP platforms are unbootable
> to the point that absolutely nothing happens after the boot loader
> transfers control.
> 
> I've not been running the boots for about a month, so I'm not sure
> when this breakage crept in.
> 
> You can see the results in the boot logs on the website.  Please
> investigate.  And I'll try without arm-soc tomorrow.
> 
> Very disappointed that the ARM kernel seems to be rather screwed at
> the moment across multiple sub-arches.

My Panda ES works with omap2plus_defconfig, but I just noticed that the
in-kernel uImage target will use a bad load/entry address so loading and
booting that uImage will hang u-boot:

Image Name:   Linux-3.8.0-rc5-00389-g120d4a8
Created:      Wed Jan 30 18:30:39 2013
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    3843912 Bytes = 3753.82 kB = 3.67 MB
Load Address: fffffff2
Entry Point:  fffffff2

Looking at the latest build and boot log for SDP (oldconfig) on your build
status site verifies that you hit that case too. :(

Wrapping by hand (which my scripts already do) produces a bootable image; just
verified both with and without device-tree on my panda.

git bisect points at a069486162a59513053cf772515217ca61727704 (ARM: OMAP2+:
Enable ARCH_MULTIPLATFORM support)

Hmm. This happens because nothing sources arch/arm/mach-*/Makefile.boot for
CONFIG_ARCH_MULTIPLATFORM builds, even if only a single platform is enabled,
since $MACHINE is empty.

It seems like most of the available options to deal with this are bad. One
thing we should never do though, is to pretend to make a working uImage
when we're not.  Maybe abort building just like in the case of multiple
load addresses?


diff --git a/arch/arm/boot/Makefile b/arch/arm/boot/Makefile
index abfce28..71768b8 100644
--- a/arch/arm/boot/Makefile
+++ b/arch/arm/boot/Makefile
@@ -68,8 +68,8 @@ else
 endif
 
 check_for_multiple_loadaddr = \
-if [ $(words $(UIMAGE_LOADADDR)) -gt 1 ]; then \
-	echo 'multiple load addresses: $(UIMAGE_LOADADDR)'; \
+if [ $(words $(UIMAGE_LOADADDR)) -ne 1 ]; then \
+	echo 'multiple (or no) load addresses: $(UIMAGE_LOADADDR)'; \
 	echo 'This is incompatible with uImages'; \
 	echo 'Specify LOADADDR on the commandline to build an uImage'; \
 	false; \



-Olof

  reply	other threads:[~2013-01-31  3:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31  1:49 Failure to boot Russell King - ARM Linux
2013-01-31  3:02 ` Olof Johansson [this message]
2013-01-31  4:19   ` Nicolas Pitre
2013-01-31  9:20     ` Russell King - ARM Linux
2013-01-31 10:40       ` Russell King - ARM Linux
2013-01-31 12:49         ` Santosh Shilimkar
2013-01-31 13:04           ` Russell King - ARM Linux
2013-01-31 14:00             ` Santosh Shilimkar
2013-01-31 14:10               ` Santosh Shilimkar
2013-01-31 14:13               ` Russell King - ARM Linux
2013-01-31 14:16                 ` Russell King - ARM Linux
2013-01-31 14:20                   ` Santosh Shilimkar
2013-01-31 14:27                     ` Russell King - ARM Linux
2013-01-31 14:43                       ` Santosh Shilimkar
2013-01-31 16:00                         ` Tony Lindgren
2013-01-31 16:19                           ` Russell King - ARM Linux
2013-01-31 16:01                       ` Fabio Estevam
2013-01-31 16:18                         ` Russell King - ARM Linux
2013-01-31 16:27                           ` Arnd Bergmann
2013-01-31 17:51                             ` [PATCH, RFC] default machine descriptor for multiplatform Arnd Bergmann
2013-01-31 18:52                               ` Stephen Warren
2013-01-31 20:57                                 ` Arnd Bergmann
2013-01-31 20:34                               ` Nicolas Pitre
2013-02-01 11:47                               ` Santosh Shilimkar
2013-02-01 12:34                                 ` Arnd Bergmann
2013-02-05 21:37                               ` Rob Herring
2013-02-05 22:23                                 ` Arnd Bergmann
2013-02-05 21:39                               ` Olof Johansson

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=20130131030203.GA8374@quad.lixom.net \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nico@fluxnic.net \
    --cc=tony@atomide.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