From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PULL] u-boot-pxa/master
Date: Fri, 28 Jun 2013 10:31:50 +0200 [thread overview]
Message-ID: <20130628103150.1aa0522e@lilith> (raw)
In-Reply-To: <201306221526.21873.marex@denx.de>
Hi Marek,
On Sat, 22 Jun 2013 15:26:21 +0200, Marek Vasut <marex@denx.de> wrote:
> The following changes since commit fbf87b1823dd5ebc2a384711ea2c677543019ece:
>
> arm: optimize relocate_code routine (2013-06-21 23:05:50 +0200)
>
> are available in the git repository at:
>
> git://git.denx.de/u-boot-pxa.git master
>
> for you to fetch changes up to 9dc8fef2583f23ca6a99c6f5e709a8b80018364f:
>
> pxa: fix memory coherency problem after relocation (2013-06-22 15:25:28 +0200)
>
> ----------------------------------------------------------------
> Mike Dunn (5):
> pxa: add support for palmtreo680 board
> pxa: palmtreo680 flash programming utility
> pxa: turn icache off in cpu_init_crit()
> pxa: use -mcpu=xscale compiler option
> pxa: fix memory coherency problem after relocation
>
> CREDITS | 4 +
> MAINTAINERS | 3 +
> arch/arm/cpu/pxa/config.mk | 2 +-
> arch/arm/cpu/pxa/start.S | 3 +-
> arch/arm/lib/relocate.S | 9 +++
> board/palmtreo680/Makefile | 34 +++++++++
> board/palmtreo680/README | 581
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> board/palmtreo680/palmtreo680.c | 148 +++++++++++++++++++++++++++++++++++
> boards.cfg | 1 +
> include/configs/palmtreo680.h | 286
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> tools/palmtreo680/flash_u-boot.c | 177
> ++++++++++++++++++++++++++++++++++++++++++
> 11 files changed, 1245 insertions(+), 3 deletions(-)
> create mode 100644 board/palmtreo680/Makefile
> create mode 100644 board/palmtreo680/README
> create mode 100644 board/palmtreo680/palmtreo680.c
> create mode 100644 include/configs/palmtreo680.h
> create mode 100644 tools/palmtreo680/flash_u-boot.c
Applied to u-boot-arm/master despite palmtreo680 build warnings as
fixes are going to come from other repos.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-06-28 8:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 13:26 [U-Boot] [PULL] u-boot-pxa/master Marek Vasut
2013-06-22 16:57 ` Albert ARIBAUD
2013-06-22 17:42 ` Mike Dunn
2013-06-22 19:21 ` Albert ARIBAUD
2013-06-23 9:05 ` Marek Vasut
2013-06-23 10:13 ` Albert ARIBAUD
2013-06-23 16:41 ` Mike Dunn
2013-06-23 19:46 ` Marek Vasut
2013-06-28 8:31 ` Albert ARIBAUD [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-23 12:54 Marek Vasut
2016-11-23 18:07 ` Tom Rini
2015-08-24 18:31 Marek Vasut
2015-08-25 2:15 ` Tom Rini
2015-03-02 10:04 Marek Vasut
2015-03-02 15:28 ` Tom Rini
2014-02-06 1:54 Marek Vasut
2014-02-19 8:03 ` Albert ARIBAUD
2014-01-13 11:42 Marek Vasut
2014-01-13 13:16 ` Albert ARIBAUD
2014-01-13 16:41 ` Albert ARIBAUD
2013-12-18 17:17 Marek Vasut
2013-12-18 18:47 ` Albert ARIBAUD
2013-12-18 18:55 ` Marek Vasut
2013-12-18 19:35 ` Tom Rini
2013-12-18 19:40 ` Marek Vasut
2013-12-18 21:02 ` Marek Vasut
2013-12-18 22:06 ` Albert ARIBAUD
2013-06-12 20:57 Marek Vasut
2013-06-13 11:04 ` Albert ARIBAUD
2012-10-16 5:16 Marek Vasut
2012-10-16 16:17 ` Albert ARIBAUD
2012-03-06 11:07 Marek Vasut
2012-03-08 7:12 ` Albert ARIBAUD
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=20130628103150.1aa0522e@lilith \
--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