From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT PULL] microblaze changes
Date: Tue, 04 Feb 2014 16:41:50 +0100 [thread overview]
Message-ID: <52F10A3E.6030305@monstr.eu> (raw)
Hi Tom,
please pull these Microblaze changes to your tree.
Thanks,
Michal
The following changes since commit 07e2822d158940a0e8ba45b6ab0344ffa1011a07:
board: nios2: Check if flash is configured before calling early_flash_cmd_reset() (2014-01-29 16:44:18 -0500)
are available in the git repository at:
git://www.denx.de/git/u-boot-microblaze.git master
for you to fetch changes up to 9d24274509cdd463992dc1fb1a2820d6a4b6d21d:
microblaze: Add SPL support (2014-02-04 16:39:50 +0100)
----------------------------------------------------------------
Michal Simek (4):
microblaze: Show u-boot banner
microblaze: Report priviledged or stack protection exception
microblaze: Enable buffer write for NOR flashes
microblaze: Add SPL support
arch/microblaze/cpu/Makefile | 1 +
arch/microblaze/cpu/exception.c | 3 +++
arch/microblaze/cpu/spl.c | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
arch/microblaze/cpu/start.S | 12 ++++++++++++
arch/microblaze/cpu/timer.c | 8 +++++++-
arch/microblaze/cpu/u-boot-spl.lds | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
arch/microblaze/include/asm/spl.h | 16 ++++++++++++++++
arch/microblaze/include/asm/u-boot.h | 1 +
arch/microblaze/lib/board.c | 18 +++++++++++++++++-
include/configs/microblaze-generic.h | 63 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
10 files changed, 231 insertions(+), 3 deletions(-)
create mode 100644 arch/microblaze/cpu/spl.c
create mode 100644 arch/microblaze/cpu/u-boot-spl.lds
create mode 100644 arch/microblaze/include/asm/spl.h
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140204/3f30c668/attachment.pgp>
next reply other threads:[~2014-02-04 15:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 15:41 Michal Simek [this message]
2014-02-04 22:03 ` [U-Boot] [GIT PULL] microblaze changes Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2014-05-06 11:35 [U-Boot] [GIT PULL] Microblaze changes Michal Simek
2014-05-06 20:54 ` Tom Rini
2015-01-21 9:34 Michal Simek
2015-01-23 21:56 ` Tom Rini
[not found] <54D8C41F.90508@monstr.eu>
2015-02-09 20:27 ` [U-Boot] [GIT PULL] microblaze changes Tom Rini
2015-04-29 8:29 [U-Boot] [GIT PULL] Microblaze changes Michal Simek
2015-04-29 14:28 ` Tom Rini
2015-11-19 12:21 Michal Simek
2015-11-19 22:07 ` Tom Rini
2016-01-14 8:51 Michal Simek
2016-01-14 13:17 ` Tom Rini
2016-01-14 13:50 ` Michal Simek
2016-01-14 20:24 ` Ricardo Ribalda Delgado
2016-01-15 7:08 ` Michal Simek
2016-01-20 13:23 ` Michal Simek
2016-01-20 13:35 ` Ricardo Ribalda Delgado
2016-01-22 14:53 ` Ricardo Ribalda Delgado
2016-01-22 18:23 ` Michal Simek
2016-01-22 18:25 ` Michal Simek
2016-01-22 18:34 ` Ricardo Ribalda Delgado
2016-01-25 9:24 ` Michal Simek
2016-01-25 15:16 ` 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=52F10A3E.6030305@monstr.eu \
--to=monstr@monstr.eu \
--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.