From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ppc4xx] Please pull git://www.denx.de/git/u-boot-ppc4xx.git
Date: Fri, 31 Oct 2008 10:51:59 +0100 [thread overview]
Message-ID: <200810311051.59958.sr@denx.de> (raw)
The following changes since commit d685b74c64a38849f1a129b3ab846fbf67dd937e:
Dave Liu (1):
74xx: use r4 instead of r2 in lock_ram_in_cache and unlock_ram_in_cache
are available in the git repository at:
git://www.denx.de/git/u-boot-ppc4xx.git master
Matthias Fuchs (6):
ppc4xx: Handle other board variant in PMC440 FPGA code
ppc4xx: Clean up PMC440 header
ppc4xx: Fix esd loadpci command
ppc4xx: Update PMC440 board configuration
ppc4xx: Fix PMC440 BSP commands
ppc4xx: Update PMC440 board support
Ricardo Ribalda Delgado (1):
ppc4xx: Merge xilinx-ppc440 and xilinx-ppc405 cfg
Stefan Roese (2):
ppc4xx: Correctly configure the GPIO pin muxing on Arches
ppc4xx: Fix spelling error in MAINTAINERS file
MAINTAINERS | 4 +-
board/avnet/fx12mm/xparameters.h | 2 +-
board/esd/common/cmd_loadpci.c | 24 +++++--
board/esd/pmc440/cmd_pmc440.c | 70 ++++++++++---------
board/esd/pmc440/fpga.c | 5 +-
board/esd/pmc440/pmc440.c | 128 +++++++++++++++++++++++++++++------
board/esd/pmc440/pmc440.h | 17 ++---
include/configs/PMC440.h | 70 ++++++++++++--------
include/configs/canyonlands.h | 12 +++-
include/configs/fx12mm.h | 3 -
include/configs/ml507.h | 6 +-
include/configs/xilinx-ppc.h | 136 ++++++++++++++++++++++++++++++++++++++
include/configs/xilinx-ppc405.h | 91 +-------------------------
include/configs/xilinx-ppc440.h | 88 ++-----------------------
14 files changed, 372 insertions(+), 284 deletions(-)
create mode 100644 include/configs/xilinx-ppc.h
next reply other threads:[~2008-10-31 9:51 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 9:51 Stefan Roese [this message]
2008-11-01 15:10 ` [U-Boot] [ppc4xx] Please pull git://www.denx.de/git/u-boot-ppc4xx.git Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2009-02-18 15:01 Stefan Roese
2009-02-18 23:52 ` Wolfgang Denk
2009-02-12 5:46 Stefan Roese
2009-02-12 7:39 ` Wolfgang Denk
2009-02-06 10:19 Stefan Roese
2009-02-07 21:40 ` Wolfgang Denk
2009-01-29 10:11 Stefan Roese
2009-02-01 20:21 ` Wolfgang Denk
2009-01-26 9:47 Stefan Roese
2009-01-27 19:54 ` Wolfgang Denk
2009-01-14 10:39 Stefan Roese
2009-01-16 8:22 ` Wolfgang Denk
2008-12-10 16:23 Stefan Roese
2008-12-12 23:37 ` Wolfgang Denk
2008-11-25 8:18 Stefan Roese
2008-11-25 10:59 ` Wolfgang Denk
2008-11-21 10:54 Stefan Roese
2008-10-24 15:36 Stefan Roese
2008-10-27 21:31 ` Wolfgang Denk
2008-10-21 15:40 Stefan Roese
2008-10-21 19:20 ` Wolfgang Denk
2008-10-13 9:18 Stefan Roese
2008-10-13 10:35 ` Wolfgang Denk
2008-09-16 18:19 Stefan Roese
2008-09-16 20:36 ` Wolfgang Denk
2008-09-17 4:00 ` Stefan Roese
2008-09-21 20:48 ` Wolfgang Denk
2008-09-22 9:09 ` Stefan Roese
2008-09-12 5:22 Stefan Roese
2008-09-12 13:24 ` Wolfgang Denk
2008-09-08 13:23 Stefan Roese
2008-09-09 0:22 ` Wolfgang Denk
2008-09-09 7:34 ` Wolfgang Denk
2008-09-03 15:24 Stefan Roese
2008-09-03 20:59 ` Wolfgang Denk
2008-08-30 9:28 Stefan Roese
2008-08-31 22:05 ` Wolfgang Denk
2008-08-22 19:42 Stefan Roese
2008-08-22 22:16 ` Wolfgang Denk
2008-08-22 4:51 Stefan Roese
2008-08-22 22:15 ` Wolfgang Denk
2008-08-13 4:49 Stefan Roese
2008-08-13 21:01 ` Wolfgang Denk
2008-08-11 4:49 Stefan Roese
2008-08-11 6:46 ` Wolfgang Denk
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=200810311051.59958.sr@denx.de \
--to=sr@denx.de \
--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.