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: Mon, 9 Mar 2015 14:14:33 +0200 [thread overview]
Message-ID: <54FD8EA9.6070301@ti.com> (raw)
In-Reply-To: <20150306162849.GH25373@bill-the-cat>
Tom,
On 06/03/15 18:28, Tom Rini wrote:
> On Fri, Mar 06, 2015 at 05:34:24PM +0200, Roger Quadros wrote:
>
>> Don't redefine fdtaddr and other values that are already defined in
>> ti_armv7_common.h. The value of fdtaddr in ti_armv7_common.h is
>> more appropriate as it allows a larger kernel image to be loaded.
>>
>> With this change, I'm able to boot linux-4.0-rc1 with device tree blob.
>>
>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>> ---
>> include/configs/omap3_beagle.h | 4 +---
>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h
>> index f25a940..3ea9b08 100644
>> --- a/include/configs/omap3_beagle.h
>> +++ b/include/configs/omap3_beagle.h
>> @@ -129,10 +129,8 @@
>> /* devices */
>>
>> #define CONFIG_EXTRA_ENV_SETTINGS \
>> - "loadaddr=0x80200000\0" \
>> - "rdaddr=0x81000000\0" \
>> + DEFAULT_LINUX_BOOT_ENV \
>> "fdt_high=0xffffffff\0" \
>> - "fdtaddr=0x80f80000\0" \
>> "usbtty=cdc_acm\0" \
>> "bootfile=uImage\0" \
>> "ramdisk=ramdisk.gz\0" \
>
> With DEFAULT_LINUX_BOOT_ENV the bootm_size variable makes sure that we
> relocate the DT within the area that the kernel will see and we don't
> need fdt_high being set either.
>
I tried without fdt_high and the board wasn't booting. So we're still missing
something for the omap3_beagle w.r.t that.
Any clues?
cheers,
-roger
next prev parent reply other threads:[~2015-03-09 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 15:34 [U-Boot] [u-boot][PATCH] omap3_beagle: Fix device tree boot Roger Quadros
2015-03-06 16:28 ` Tom Rini
2015-03-09 12:14 ` Roger Quadros [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-05 13:57 Roger Quadros
2014-11-05 14:18 ` Tom Rini
2014-11-05 14:25 ` Roger Quadros
2014-11-05 15:23 ` Tom Rini
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=54FD8EA9.6070301@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox