From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] OMAP5912 -- Status? -- Identified as ARM926EJS start.S problem
Date: Thu, 19 May 2011 14:10:10 +0300 [thread overview]
Message-ID: <4DD4FA92.6040001@compulab.co.il> (raw)
In-Reply-To: <66F0ABBCB3D267479CB73B0F4C78908F02739008@ellex-adc1>
On 05/19/11 11:12, James Harris wrote:
> Hi Igor,
>
> Thanks for your prompt response.
> I've made similar modifications to the omap5912osk over the past number of days with no success...
:(
> The problem appears deeper than just providing these definitions, which as you say, requires actual hardware to test with :)
Exactly, I had to make it compile so I can compile test some other patch.
So I took some values from another board with the same SoC that looked sane to me.
And put there a "FIXME" comment...
> I've gone back to 2010.09 release and it now works very nicely!
>
> I chose that version as it is just prior to the relocation changes applied in the arch/arm/cpu/arm926ejs/start.S file:
> 2010-09-19 Heiko Schocher ARM: implement relocation for ARM926
>
> That change would certainly cause out-of-box compilation failures, however I am not sure whether it was that change or possibly the following change:
> 2010-10-13 Albert Aribaud arm: implement ELF relocations
> that causes the runtime failure...
Added Heiko and Albert to cc.
> I may investigate further, however, at this stage I can "move on" using the 2010.09 release.
>
> As an aside: Using U-Boot 2010.09 also resolves a problem I was having with u-boot V1.1.1:
> The V2.6.32 linux kernel could not be booted when mem=32M was passed using u-boot V1.1.1
> However when I tried earlier today, through pure desperation, passing mem=16M it did boot.
> Now under u-boot 2010.09 the Linux kernel boots just fine with mem=32M
>
> Cheers,
>
> James
>
>
> .......................................................................
>
> James Harris
>
> T +61 8 8104 5253
> E jharris at ellex.com
> .......................................................................
>
> -----Original Message-----
> From: Igor Grinberg [mailto:grinberg at compulab.co.il]
> Sent: Thursday, 19 May 2011 5:09 PM
> To: James Harris
> Cc: u-boot at lists.denx.de; rishi at ti.com
> Subject: Re: [U-Boot] OMAP5912 -- Status?
>
> Hi James,
>
> On 05/19/11 10:07, James Harris wrote:
>
>> Greetings all,
>>
>>
>>
>> Over the past few days I've been trying to get u-boot 2011.03 for the
>> omap5912osk working.
>>
>>
>>
>> Support for the target appears to have stagnated...
>>
>>
>>
>> "Out of the box" the omap5912osk (and omap1610inn) target fails to
>> compile due to the following missing symbols:
>>
>> CONFIG_SYS_SDRAM_BASE
>>
>> CONFIG_SYS_INIT_SP_ADDR
> I've send a patch [1] which hopefully fixes omap1610inn and omap1610h2.
> I can't test is as I don't have this hardware.
> It is currently waiting for Sandeep's approval.
>
> [1]
> http://www.mail-archive.com/u-boot at lists.denx.de/msg52157.html
>
>
>
> --
> Regards,
> Igor.
>
>
--
Regards,
Igor.
next prev parent reply other threads:[~2011-05-19 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 8:12 [U-Boot] OMAP5912 -- Status? -- Identified as ARM926EJS start.S problem James Harris
2011-05-19 11:10 ` Igor Grinberg [this message]
2011-05-19 18:56 ` Wolfgang Denk
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=4DD4FA92.6040001@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=u-boot@lists.denx.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