From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 0/6] OMAP: fix build breaks on OMAP boards
Date: Mon, 13 Jun 2011 12:59:12 +0200 [thread overview]
Message-ID: <4DF5ED80.80207@aribaud.net> (raw)
In-Reply-To: <1307618650-787-1-git-send-email-aneesh@ti.com>
Hi Aneesh,
Le 09/06/2011 13:24, Aneesh V a ?crit :
> Fix build breaks for OMAP boards.
> All the build breaks were due to couple of missing
> defines in the config file, namely:
>
> CONFIG_SYS_SDRAM_BASE and CONFIG_SYS_INIT_SP_ADDR
>
> They have been fixed by providing the right SDRAM
> base address and by using SRAM base as the initial
> stack address.
>
> None of these have been tested as I do not have any of
> these boards.
>
> V2:
> * Replaced the magic number used for CONFIG_SYS_INIT_SP_ADDR
> with a symbolic name - PHYS_SRAM - indicating that SRAM is
> used for the intial stack. Made this change in all the
> patches.
> V3:
> * Missed doing the V2 change for omap1610inn. Fixed that
>
> Aneesh V (6):
> omap1610h2: fix build breaks
> omap5912osk: fix build breaks
> omap1510inn: fix build breaks
> omap1610inn: fix build breaks
> omap2420h4: fix build breaks
> omap730p2: fix build breaks
>
> include/configs/omap1510inn.h | 5 +++++
> include/configs/omap1610h2.h | 5 +++++
> include/configs/omap1610inn.h | 5 +++++
> include/configs/omap2420h4.h | 4 ++++
> include/configs/omap5912osk.h | 5 +++++
> include/configs/omap730p2.h | 5 +++++
> 6 files changed, 29 insertions(+), 0 deletions(-)
Hmm, seems like they don't apply cleanly above current
u-boot-arm/master. Can you rebase and resend as V4 ?
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-06-13 10:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 15:13 [U-Boot] [PATCH 0/6] OMAP: fix build breaks on OMAP boards Aneesh V
2011-06-07 15:13 ` [U-Boot] [PATCH 1/6] omap1610h2: fix build breaks Aneesh V
2011-06-07 15:13 ` [U-Boot] [PATCH 2/6] omap5912osk: " Aneesh V
2011-06-07 15:13 ` [U-Boot] [PATCH 3/6] omap1510inn: " Aneesh V
2011-06-07 15:13 ` [U-Boot] [PATCH 4/6] omap1610inn: " Aneesh V
2011-06-07 15:13 ` [U-Boot] [PATCH 5/6] omap2420h4: " Aneesh V
2011-06-07 15:13 ` [U-Boot] [PATCH 6/6] omap730p2: " Aneesh V
2011-06-08 20:20 ` [U-Boot] [PATCH 0/6] OMAP: fix build breaks on OMAP boards Albert ARIBAUD
2011-06-09 7:52 ` Aneesh V
2011-06-09 8:24 ` Aneesh V
2011-06-09 8:24 ` [U-Boot] [PATCH 1/6] omap1610h2: fix build breaks Aneesh V
2011-06-09 8:24 ` [U-Boot] [PATCH 2/6] omap5912osk: " Aneesh V
2011-06-09 8:24 ` [U-Boot] [PATCH 3/6] omap1510inn: " Aneesh V
2011-06-09 8:24 ` [U-Boot] [PATCH 4/6] omap1610inn: " Aneesh V
2011-06-09 8:24 ` [U-Boot] [PATCH 5/6] omap2420h4: " Aneesh V
2011-06-09 8:24 ` [U-Boot] [PATCH 6/6] omap730p2: " Aneesh V
2011-06-09 11:24 ` [U-Boot] [PATCH v3 0/6] OMAP: fix build breaks on OMAP boards Aneesh V
2011-06-13 10:59 ` Albert ARIBAUD [this message]
2011-06-13 11:12 ` Aneesh V
2011-06-13 11:17 ` Aneesh V
2011-06-13 11:58 ` Albert ARIBAUD
2011-06-09 11:24 ` [U-Boot] [PATCH v3 1/6] omap1610h2: fix build breaks Aneesh V
2011-06-09 11:24 ` [U-Boot] [PATCH v3 2/6] omap5912osk: " Aneesh V
2011-06-09 11:24 ` [U-Boot] [PATCH v3 3/6] omap1510inn: " Aneesh V
2011-06-09 11:24 ` [U-Boot] [PATCH v3 4/6] omap1610inn: " Aneesh V
2011-06-09 11:24 ` [U-Boot] [PATCH v3 5/6] omap2420h4: " Aneesh V
2011-06-09 11:24 ` [U-Boot] [PATCH v3 6/6] omap730p2: " Aneesh V
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=4DF5ED80.80207@aribaud.net \
--to=albert.u.boot@aribaud.net \
--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