From: dugo@xs4all.nl (Jacob Goense)
Subject: [TUHS] jor1k was:Re: Need your help for 2019
Date: Mon, 06 Mar 2017 15:15:32 +0100 [thread overview]
Message-ID: <20ae194033e11ba5833834a6d331843b@xs4all.nl> (raw)
In-Reply-To: <51EE9B29-09E2-4626-8B71-E5FD7857D0B4@superglobalmegacorp.com>
moved.
On 2017-03-06 04:44, Jason Stevens wrote:
> That ooenrisc is pretty cool too!
>
> https://s-macke.github.io/jor1k/demos/main.html
Yes, I love it. Unfortunately upstreaming the or1k patches
to GCC failed due to copyright assignment issues or it
would be running debian now. I run a bare minimum static
cross linux from scratch on it.
This builds the toolchain, kernel and a few bits like simh
https://github.com/dugoh/tcb
This continues from above to add more things to sysroot
https://github.com/dugoh/srb
This fork ties it together
https://github.com/dugoh/jor1k
Apologies in advance for the horrendous state of my commit
history. I abuse github as a scratch pad and CD pipeline,
(github -> travis -> gh-pages) and never bothered with any
of the courtesies of open source development.
> It apparently has network support as well!
The network back-end is here
https://github.com/benjamincburns/websockproxy
Easy to set up if you do Docker and otherwise not that hard.
next prev parent reply other threads:[~2017-03-06 14:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 3:16 [TUHS] " Warren Toomey
2017-03-04 3:41 ` Steve Johnson
2017-03-04 4:15 ` Cory Smelosky
2017-03-04 4:20 ` Warren Toomey
2017-03-04 4:49 ` Cory Smelosky
2017-03-04 8:21 ` Paul Ruizendaal
2017-03-04 8:24 ` jsteve
2017-03-06 0:57 ` Paul Ruizendaal
2017-03-06 3:44 ` Jason Stevens
2017-03-06 11:16 ` Paul Ruizendaal
[not found] ` <20170306113704.GA14536@minnie.tuhs.org>
2017-03-06 13:25 ` Paul Ruizendaal
2017-03-06 14:15 ` Jacob Goense [this message]
2017-03-04 11:09 ` Jacob Goense
2017-03-04 17:41 ` Charles Anthony
2017-03-06 17:51 ` John Floren
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=20ae194033e11ba5833834a6d331843b@xs4all.nl \
--to=dugo@xs4all.nl \
/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;
as well as URLs for NNTP newsgroup(s).