All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [u-boot][PATCH] omap3_beagle: Fix device tree boot
Date: Wed, 5 Nov 2014 16:25:55 +0200	[thread overview]
Message-ID: <545A3373.5060202@ti.com> (raw)
In-Reply-To: <20141105141800.GD15133@bill-the-cat>

On 11/05/2014 04:18 PM, Tom Rini wrote:
> On Wed, Nov 05, 2014 at 03:57:34PM +0200, Roger Quadros wrote:
> 
>> Push the device tree blob load address (fdtaddr) further apart than
>> kernel load address (loadaddr) to accomodate a larger kernel image.
>> We set fdtaddr to the same value as set in ti_armv7_common.h.
>>
>> With this change, I'm able to boot linux-3.18-rc1 zImage built using
>> omap2plus_defconfig.
>>
>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>> ---
>>  include/configs/omap3_beagle.h | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h
>> index f25a940..5ea048a 100644
>> --- a/include/configs/omap3_beagle.h
>> +++ b/include/configs/omap3_beagle.h
>> @@ -132,7 +132,7 @@
>>  	"loadaddr=0x80200000\0" \
>>  	"rdaddr=0x81000000\0" \
>>  	"fdt_high=0xffffffff\0" \
>> -	"fdtaddr=0x80f80000\0" \
>> +	"fdtaddr=0x88000000\0" \
> 
> While we're in here whacking these values lets make this match up the
> rest of the values we use in ti_armv7_common.h (so drop fdt_high and set
> bootm_size and so forth).  Thanks!
> 
It seems like omap3_beagle.h includes ti_omap3_common.h which in turn includes
ti_armv7_common.h.

So I just need to remove the duplicate definitions from omap3_beagle.h

cheers,
-roger

  reply	other threads:[~2014-11-05 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05 13:57 [U-Boot] [u-boot][PATCH] omap3_beagle: Fix device tree boot Roger Quadros
2014-11-05 14:18 ` Tom Rini
2014-11-05 14:25   ` Roger Quadros [this message]
2014-11-05 15:23     ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2015-03-06 15:34 Roger Quadros
2015-03-06 16:28 ` Tom Rini
2015-03-09 12:14   ` Roger Quadros

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=545A3373.5060202@ti.com \
    --to=rogerq@ti.com \
    --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 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.