public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Sricharan R <r.sricharan@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 0/5] ARM: OMAP: Cleanup save_boot_params function
Date: Mon, 3 Jun 2013 11:39:37 +0530	[thread overview]
Message-ID: <51AC3321.1060109@ti.com> (raw)
In-Reply-To: <20130531142210.GS11917@bill-the-cat>

Hi Tom,

On Friday 31 May 2013 07:52 PM, Tom Rini wrote:
> On Fri, May 31, 2013 at 10:18:46AM -0400, Tom Rini wrote:
>> On Wed, Apr 24, 2013 at 04:11:20PM +0530, Sricharan R wrote:
>>
>>> The save_boot_params function does not store the data in a
>>> always writable area. So the code is broken for a 'XIP' boot.
>>> This series corrects this by storing it in 'gd' and also
>>> adds a 'C' equivalent function for the same. The essential cleanups
>>> for the same are added in this.
>>>
>>> Tested this on omap5 uevm board with SD/EMMC boot.
>>> omap4/5 boards does not have a XIP flash.
>>> So yet to test XIP with this series.
>>>
>>> Also verfied a MAKEALL for armv7.
>> OK, do you have a beaglebone or am335x_evm around?  This switch up
>> breaks them, and I'm not sure what's going on.  Part of the issue is
>> that the NON_SECURE_SRAM_START/END weren't quite right, but they weren't
>> so wrong as to be a problem (END wasn't quite the end, and start was in
>> the middle of our image, but we didn't reference it).  I'm going to keep
>> poking at this as well.  Thanks!
> Answered my own question now, am33xx (andti81xx) doesn't opt-in for
> omap-common/hwinit-common.c
>
 Ok, Thanks for the pointer. So i will add this in the series.
 and boot test once on am33xx

Regards,
 Sricharan

  reply	other threads:[~2013-06-03  6:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 10:41 [U-Boot] [PATCH V2 0/5] ARM: OMAP: Cleanup save_boot_params function Sricharan R
2013-04-24 10:41 ` [U-Boot] [PATCH V2 1/5] ARM: OMAP: Make omap_boot_parameters common across socs Sricharan R
2013-04-24 10:41 ` [U-Boot] [PATCH V2 2/5] ARM: OMAP4/5: Make OMAPx_SRAM_SCRATCH_ defines common Sricharan R
2013-04-24 10:41 ` [U-Boot] [PATCH V2 3/5] ARM: OMAP: Correct save_boot_params and replace with 'C' function Sricharan R
2013-04-24 10:41 ` [U-Boot] [PATCH V2 4/5] ARM: OMAP: Cleanup boot parameters usage Sricharan R
2013-05-08 17:56   ` Tom Rini
2013-04-24 10:41 ` [U-Boot] [PATCH V2 5/5] ARM: OMAP: Add arch_cpu_init function Sricharan R
2013-05-08 17:56   ` Tom Rini
2013-05-08  9:20 ` [U-Boot] [PATCH V2 0/5] ARM: OMAP: Cleanup save_boot_params function Sricharan R
2013-05-08 17:56   ` Tom Rini
2013-05-09  6:04     ` Sricharan R
2013-05-31 14:18 ` Tom Rini
2013-05-31 14:22   ` Tom Rini
2013-06-03  6:09     ` Sricharan R [this message]
2013-06-03  7:26       ` Sricharan R

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=51AC3321.1060109@ti.com \
    --to=r.sricharan@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