10:17 p.m.
I'm wondering a bit about the branching strategy. I'm currently stockpiling
a bunch of small patches and I wonder if those should be submitted against
master, minion-v0.4 or ethernet-v0.5.
//Olof
10:28 p.m.
On Thu, Nov 23, 2017 at 2:18 PM, Philipp Wagner <lists(a)philipp-wagner.com>
wrote:
On 11/23/2017 02:17 PM, Olof Kindgren wrote:
> I'm wondering a bit about the branching strategy. I'm currently
> stockpiling
> a bunch of small patches and I wonder if those should be submitted against
> master, minion-v0.4 or ethernet-v0.5.
>
How about worlddomination-v1.0?
Philipp
I need to learn how to command my minions before I can use the
worlddomination branch
//Olof
10:40 p.m.
We expect ethernet-v0.5 to be the last release on this development series,
except for bug fixes. It is a lineal development of minion-v0.4. It has
not been
merged to master because we expect the long awaited update of Rocket to
become
the new master. This update is languishing in the update branch at the
moment,
and does not work yet. When it does all the functionality of
ethernet-v0.5 will be folded
in to this and become the new master. So I think ethernet-v0.5 will be
the last stable release
for a while, and we may well jump straight to v1.0 for the next release
after that. This release
will have minimal changes from the Chisel codebase and will be lacking
the security enhancements.
So if you just want a safe, incremental experience I would adopt the
ethernet-v0.5 as your base,
but if you want to dive in to the very latest code with compressed
instructions, run-control debugging
and programmable interrupts, then the update branch is for you, and you
will be working at ISA
simulation level, not operational FPGA emulation level. If you are doing
something specifically
with Minions, stick to the minion-v0.4 release.
On 23/11/17 13:17, Olof Kindgren wrote:
I'm wondering a bit about the branching strategy. I'm
currently stockpiling
a bunch of small patches and I wonder if those should be submitted against
master, minion-v0.4 or ethernet-v0.5.
//Olof
10:51 p.m.
Safe and incremental suits me fine, as I don't really care about the ISA
changes at this point. I probably want to do some work on the minions at
some point, but I'll stick to 0.5 for now.
Thanks, expect some patches for the ethernet-v0.5 branch
//Olof
On Thu, Nov 23, 2017 at 2:40 PM, Dr Jonathan Kimmitt <jrrk2(a)cam.ac.uk>
wrote:
We expect ethernet-v0.5 to be the last release on this development
series,
except for bug fixes. It is a lineal development of minion-v0.4. It has
not been
merged to master because we expect the long awaited update of Rocket to
become
the new master. This update is languishing in the update branch at the
moment,
and does not work yet. When it does all the functionality of ethernet-v0.5
will be folded
in to this and become the new master. So I think ethernet-v0.5 will be the
last stable release
for a while, and we may well jump straight to v1.0 for the next release
after that. This release
will have minimal changes from the Chisel codebase and will be lacking the
security enhancements.
So if you just want a safe, incremental experience I would adopt the
ethernet-v0.5 as your base,
but if you want to dive in to the very latest code with compressed
instructions, run-control debugging
and programmable interrupts, then the update branch is for you, and you
will be working at ISA
simulation level, not operational FPGA emulation level. If you are doing
something specifically
with Minions, stick to the minion-v0.4 release.
On 23/11/17 13:17, Olof Kindgren wrote:
> I'm wondering a bit about the branching strategy. I'm currently
> stockpiling
> a bunch of small patches and I wonder if those should be submitted against
> master, minion-v0.4 or ethernet-v0.5.
>
> //Olof
>
2135
days inactive
2135
days old
4 comments
3 participants
participants (3)
-
Dr Jonathan Kimmitt -
Olof Kindgren -
Philipp Wagner