From: mpfj-list@mimc.co.uk (Mark Jackson)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.7-rc3
Date: Thu, 01 Nov 2012 15:52:07 +0000 [thread overview]
Message-ID: <50929AA7.80401@mimc.co.uk> (raw)
In-Reply-To: <509134A4.708@mimc.co.uk>
On 31/10/12 14:24, Mark Jackson wrote:
> On 31/10/12 13:57, Hiremath, Vaibhav wrote:
>> On Wed, Oct 31, 2012 at 19:11:03, Mark Jackson wrote:
>>>
>>> If I try the latest mainline U-Boot (or the TI branch), I just get to "Starting kernel ..." and then
>>> hangs.
>>>
>>
>>
>> I am using Mainline u-boot and it works for me. Can you paste u-boot boot
>> log and environment variable here?
>
> ------------------------
> mainline U-Boot boot log
> ------------------------
> U-Boot SPL 2012.10-00434-ged296d2 (Oct 31 2012 - 14:18:50)
> OMAP SD/MMC: 0
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2012.10-00434-ged296d2 (Oct 31 2012 - 14:18:50)
>
> I2C: ready
> DRAM: 256 MiB
> WARNING: Caches not enabled
> MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Using default environment
>
> Net: cpsw
> Hit any key to stop autoboot: 0
> mmc0 is current device
> SD/MMC found on device 0
> reading uEnv.txt
> 29 bytes read
> Loaded environment from uEnv.txt
> Importing environment from mmc ...
> 4315695 bytes read
> Booting from mmc ...
> ## Booting kernel from Legacy Image at 80200000 ...
> Image Name: Linux-3.7.0-rc1-47802-ge7289dc-d
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 4308448 Bytes = 4.1 MiB
> Load Address: 80008000
> Entry Point: 80008000
> Verifying Checksum ... OK
> Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> ------------------------
> Contents of uEnv.txt
> --------------------
> mmcrootfstype=ext2 rootwait
Vaibhav
Does this boot log shed any light on my non-boot problem ?
Are we using the same U-Boot version (2012.10-00434-ged296d2) ?
Can you post your linux-ohporter .config ?
I was also thinking, if the previously mentioned patch [1] was concerning toolchains, what toolchain
are you using ? I'm using the latest mainline Buildroot git, which compiles gcc version 4.5.4
(Buildroot 2012.11-git-00497-ge48bf89).
[1] - http://www.spinics.net/lists/linux-omap/msg79911.html
Cheers
Mark J.
next prev parent reply other threads:[~2012-11-01 15:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 2:36 OMAP baseline test results for v3.7-rc3 Paul Walmsley
2012-10-30 4:39 ` Vaibhav Hiremath
2012-10-30 13:03 ` Paul Walmsley
2012-11-05 2:41 ` Paul Walmsley
2012-11-06 6:09 ` Hiremath, Vaibhav
2012-11-06 10:24 ` Hiremath, Vaibhav
2012-10-30 10:55 ` Mark Jackson
2012-10-30 11:47 ` Paul Walmsley
2012-10-30 12:39 ` Hiremath, Vaibhav
2012-10-30 14:48 ` Vaibhav Hiremath
2012-10-30 16:27 ` Tony Lindgren
2012-10-30 17:27 ` Felipe Balbi
2012-10-30 17:58 ` Tony Lindgren
2012-10-30 18:51 ` Felipe Balbi
2012-11-06 6:17 ` Hiremath, Vaibhav
2012-11-06 7:58 ` Felipe Balbi
2012-11-06 8:07 ` Hiremath, Vaibhav
2012-11-06 8:05 ` Felipe Balbi
2012-10-31 13:41 ` Mark Jackson
2012-10-31 13:57 ` Hiremath, Vaibhav
2012-10-31 14:24 ` Mark Jackson
2012-11-01 15:52 ` Mark Jackson [this message]
2012-11-05 16:54 ` Mark Jackson
2012-11-06 6:16 ` Hiremath, Vaibhav
2012-11-06 9:47 ` Mark Jackson
2012-11-13 15:26 ` Mark Jackson
2012-11-13 15:35 ` Paul Walmsley
2012-11-13 15:57 ` Mark Jackson
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=50929AA7.80401@mimc.co.uk \
--to=mpfj-list@mimc.co.uk \
--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).