From: "Hemanth V" <hemanthv@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>, linux-omap@vger.kernel.org
Subject: Re: L-O master branch broken ?
Date: Thu, 18 Jun 2009 20:17:10 +0530 [thread overview]
Message-ID: <006701c9f023$aa55a170$LocalHost@wipultra793> (raw)
In-Reply-To: 20090618102237.GI8482@atomide.com
----- Original Message -----
From: "Tony Lindgren" <tony@atomide.com>
To: "Hemanth V" <hemanthv@ti.com>
Cc: "Kevin Hilman" <khilman@deeprootsystems.com>;
<linux-omap@vger.kernel.org>
Sent: Thursday, June 18, 2009 3:52 PM
Subject: Re: L-O master branch broken ?
>* Hemanth V <hemanthv@ti.com> [090618 13:39]:
>> ----- Original Message ----- From: "Tony Lindgren" <tony@atomide.com>
>>
>>
>>>> I get the below error while compiling 3430SDP. I see below commit as
>>>> the
>>>> latest one.
>>
>>>
>>> Thanks, pushing a fix right now with the missing brace missing from
>>> Kevin's
>>> sram.c patch. Also moved around the defines so sram.c build for omap1.
>>>
>>
>> Booting still seems to have problems. Its hung after start kernel
>>
>>
>> Bytes transferred = 2480664 (25da18 hex)
>> ## Booting image at 80000000 ...
>> Image Name: Linux-2.6.30-omap1-06022-g6f4712
>> Image Type: ARM Linux Kernel Image (uncompressed)
>> Data Size: 2480600 Bytes = 2.4 MB
>> Load Address: 80008000
>> Entry Point: 80008000
>> Verifying Checksum ... OK
>> OK
>>
>> Starting kernel ...
>>
>
> Can you see what happens with DEBUG_LL enabled?
Doesn't seem to show any additional messages even with
DEBUG_LL enabled
next prev parent reply other threads:[~2009-06-18 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 9:35 L-O master branch broken ? Hemanth V
2009-06-18 7:52 ` Tony Lindgren
2009-06-18 10:38 ` Hemanth V
2009-06-18 10:22 ` Tony Lindgren
2009-06-18 14:47 ` Hemanth V [this message]
2009-06-18 15:31 ` Kevin Hilman
2009-06-18 23:10 ` Aguirre Rodriguez, Sergio Alberto
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='006701c9f023$aa55a170$LocalHost@wipultra793' \
--to=hemanthv@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--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