From: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/9] Add support for the OpenRISC architecture
Date: Mon, 19 Dec 2011 10:20:08 +0200 [thread overview]
Message-ID: <20111219082008.GA30446@chokladfabriken.org> (raw)
In-Reply-To: <1322370297-22892-1-git-send-email-stefan.kristiansson@saunalahti.fi>
Hi Wolfgang,
On Sun, Nov 27, 2011 at 07:04:48AM +0200, Stefan Kristiansson wrote:
> This patch series adds support for the OpenRISC 1000 architecture.
>
> The OpenRISC architecture has been around for about a decade and
> has experienced a revival in the last couple of years from the
> efforts of a small, but dedicated community compound of both
> commercial and independent contributors.
>
> Most of the development takes place on opencores.org/or1k and openrisc.net.
>
> The patches included in this series are also available in the
> 'for-upstream' branch in the following git repository:
>
> git://openrisc.net/stefan/u-boot
>
> which is also browsable here:
>
> http://git.openrisc.net/cgit.cgi/stefan/u-boot/?h=for-upstream
>
> NOTE: The openrisc-generic board depends on this pending
> patch to build properly:
> net/ethoc: use flush_dcache_range instead of flush_dcache
> (http://patchwork.ozlabs.org/patch/123622/)
I have not received any comments (or complaints, depending how
you look at it) on the v2 of those patches.
I saw your message about the next branch, so would you
please consider applying those to that, if nobody has any further
comments or objections?
Thanks
Stefan
prev parent reply other threads:[~2011-12-19 8:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-27 5:04 [U-Boot] [PATCH v2 0/9] Add support for the OpenRISC architecture Stefan Kristiansson
2011-11-27 5:04 ` [U-Boot] [PATCH v2 1/9] openrisc: Add architecture header files Stefan Kristiansson
2012-01-13 20:29 ` Wolfgang Denk
2011-11-27 5:04 ` [U-Boot] [PATCH v2 2/9] openrisc: Add architecture image support Stefan Kristiansson
2012-01-13 20:29 ` Wolfgang Denk
2011-11-27 5:04 ` [U-Boot] [PATCH v2 3/9] openrisc: Add cpu files Stefan Kristiansson
2011-12-22 9:09 ` Michal Simek
2011-12-22 11:39 ` Stefan Kristiansson
2012-01-05 23:15 ` Mike Frysinger
2012-01-06 13:22 ` Stefan Kristiansson
2012-01-06 19:27 ` Mike Frysinger
2012-01-13 20:29 ` Wolfgang Denk
2011-11-27 5:04 ` [U-Boot] [PATCH v2 4/9] openrisc: Add library functions Stefan Kristiansson
2012-01-13 20:29 ` Wolfgang Denk
2011-11-27 5:04 ` [U-Boot] [PATCH v2 5/9] openrisc: Add board info printout to cmd_bdinfo Stefan Kristiansson
2012-01-13 20:29 ` Wolfgang Denk
2011-11-27 5:04 ` [U-Boot] [PATCH v2 6/9] openrisc: Add support for standalone programs Stefan Kristiansson
2012-01-13 20:29 ` Wolfgang Denk
2011-11-27 5:04 ` [U-Boot] [PATCH v2 7/9] openrisc: Add openrisc-generic example board Stefan Kristiansson
2012-01-13 20:30 ` Wolfgang Denk
2011-11-27 5:04 ` [U-Boot] [PATCH v2 8/9] openrisc: Add architecture to MAKEALL Stefan Kristiansson
2012-01-13 20:30 ` Wolfgang Denk
2011-11-27 5:04 ` [U-Boot] [PATCH v2 9/9] openrisc: Add MAINTAINERS entry Stefan Kristiansson
2012-01-13 20:30 ` Wolfgang Denk
2011-12-19 8:20 ` Stefan Kristiansson [this message]
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=20111219082008.GA30446@chokladfabriken.org \
--to=stefan.kristiansson@saunalahti.fi \
--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