Commit d01e1f35 authored by Stafford Horne's avatar Stafford Horne
Browse files

openrisc: Updates after has been lost

The domain expired and was taken over by squatters.
These updates point documentation to the new domain, mailing lists
and git repos.

Also, Jonas is not the main maintainer anylonger, he reviews changes
but does not maintain a repo or sent pull requests.  Updating this to
add Stafford and Stefan who are the active maintainers.

Acked-by: default avatarOlof Kindgren <>
Signed-off-by: default avatarStafford Horne <>
parent 266c7fad
......@@ -8968,9 +8968,11 @@ F: drivers/of/resolver.c
M: Jonas Bonn <>
M: Stefan Kristiansson <>
M: Stafford Horne <>
S: Maintained
T: git git://
F: arch/openrisc/
......@@ -6,7 +6,7 @@ target architecture, specifically, is the 32-bit OpenRISC 1000 family (or1k).
For information about OpenRISC processors and ongoing development:
For more information about Linux on OpenRISC, please contact South Pole AB.
......@@ -24,17 +24,17 @@ In order to build and run Linux for OpenRISC, you'll need at least a basic
toolchain and, perhaps, the architectural simulator. Steps to get these bits
in place are outlined here.
1) The toolchain can be obtained from Instructions for building
1) The toolchain can be obtained from Instructions for building
a toolchain can be found at:
2) or1ksim (optional)
or1ksim is the architectural simulator which will allow you to actually run
your OpenRISC Linux kernel if you don't have an OpenRISC processor at hand.
git clone git://
git clone
cd or1ksim
./configure --prefix=$OPENRISC_PREFIX
......@@ -295,7 +295,7 @@ void __init setup_arch(char **cmdline_p)
*cmdline_p = boot_command_line;
printk(KERN_INFO "OpenRISC Linux --\n");
printk(KERN_INFO "OpenRISC Linux --\n");
static int show_cpuinfo(struct seq_file *m, void *v)
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment