* [libre-riscv-dev] [Bug 307] New: look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-05-11 12:28 UTC (permalink / raw)
To: libre-riscv-dev
https://bugs.libre-soc.org/show_bug.cgi?id=307
Bug ID: 307
Summary: look at installing a kan-ban board on top of bugzilla
Product: Libre-RISC-V Website
Version: unspecified
Hardware: PC
OS: Mac OS
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: website
Assignee: lkcl@lkcl.net
Reporter: lkcl@lkcl.net
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
example such as this https://github.com/leif81/bzkanban
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-05-11 12:28 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=307
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|lkcl@lkcl.net |addw@phcomp.co.uk
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-05-11 12:43 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=307
--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://github.com/mozilla/kanbanzilla huge weird mixture of dependencies, nice
concept, far too many dependencies (node, ruby, python - wtf??)
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-11 13:23 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #37 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #33)
> i haven't committed it (i leave it to you to evaluate)
> this passes the tests nosetests3 decoder/isa/test_caller.py
>
> register RA is read in - however it's not involved in the datapath for RB.
>
> here's the pseudocode
>
> * rlwinm RA,RS,SH,MB,ME (Rc=0)
> * rlwinm. RA,RS,SH,MB,ME (Rc=1)
>
> n <- SH
> r <- ROTL32((RS)[32:63], n)
> m <- MASK(MB+32, ME+32)
> RA <- r & m
>
> * rlwnm RA,RS,RB,MB,ME (Rc=0)
> * rlwnm. RA,RS,RB,MB,ME (Rc=1)
>
> n <- (RB)[59:63]
> r <- ROTL32((RS)[32:63], n)
> m <- MASK(MB+32, ME+32)
> RA <- r & m
>
> the only difference is in n
>
> both are 5 bit, SH should be coming from the immediate-decoding, (RB)[59:63]
> means get the 5 LSBs of RB.
>
> i believe we're ok making the change below. it doesn't make sense that IBM
> would design something that needs a special exception path for the immediate,
> just for one instruction.
Look at rlwimi:
n <- SH
r <- ROTL32(RS[32:63], n)
m <- MASK(MB+32, ME+32)
RA <- r & m | (RA) & ~m
It definitely does require reading in RS, RA, and SH
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] daily kan-ban update 11may2020
From: Michael Nolan @ 2020-05-11 13:32 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDy1K5K=AF_LT=A24JJiC=5Jum+412Kup4SpQD3ngW+SmQ@mail.gmail.com>
On 5/11/20 8:26 AM, Luke Kenneth Casson Leighton wrote:
> btw i forgot to mention: here's what kan-ban is supposed to be :)
> https://en.wikipedia.org/wiki/Kanban_(development)
Well that explains some things. When I googled it I came up with the
manufacturing version and was rather confused what that had to do with us.
Yesterday (and saturday) I worked on the integer ALU adding support for
shifts and rotates. Today I'd like to improve the ALU testbench some, so
instead of blindly reading and writing registers based on hardcoded
numbers it actually looks at the ones used by the instruction.
(Basically, have it simulate the register file). I'd also like to add in
support for carry, overflow, and condition registers.
--Michael
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-11 14:31 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #38 from Michael Nolan <mtnolan2640@gmail.com> ---
Ugh. I added support to the alu testbench for reading the registers specified
in the instruction, instead of hardcoding them to 1, 2, and 3. I have it read
the register select ports in the decoder in the order [3, 1, 2], and the first
2 with valid data end up in the a and b inputs of the ALU. I'm a bit annoyed
about the weird order, but everything seems to work
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-11 15:51 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #39 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #37)
> Look at rlwimi:
>
> n <- SH
> r <- ROTL32(RS[32:63], n)
> m <- MASK(MB+32, ME+32)
> RA <- r & m | (RA) & ~m
>
> It definitely does require reading in RS, RA, and SH
that's ok - yes it reads RS, RA and SH. what it doesn't do is need to
switch off RB imm decoding. at least, let me put it this way:
the unit test passes fine with that patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-11 16:03 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #40 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #38)
> Ugh. I added support to the alu testbench for reading the registers
> specified in the instruction, instead of hardcoding them to 1, 2, and 3. I
> have it read the register select ports in the decoder in the order [3, 1,
> 2], and the first 2 with valid data end up in the a and b inputs of the ALU.
> I'm a bit annoyed about the weird order, but everything seems to work
hmmm hmmm hang on hang on - this is removing the order. if there's 3 regs,
then 3 regs are needed.
what's needed is like this:
inputs = []
reg3_ok = yield dec2.e.read_reg3.ok
reg3_sel = 0
if reg3_ok:
reg3_sel = yield dec2.e.read_reg3.data
reg3_sel = (sim.gpr(reg3_sel).value
inputs.append(reg3_sel, reg3_ok)
...
...
followed by:
yield alu.p.data_i.a.eq(input[0][0]) # RA
yield alu.p.data_i.b.eq(input[1][0]) # RB
yield alu.p.data_i.c.eq(input[2][0]) # RC
def set_alu_inputs(alu, dec2, sim):
inputs = []
reg3_ok = yield dec2.e.read_reg3.ok
if reg3_ok:
reg3_sel = yield dec2.e.read_reg3.data
inputs.append(sim.gpr(reg3_sel).value)
reg1_ok = yield dec2.e.read_reg1.ok
if reg1_ok:
reg1_sel = yield dec2.e.read_reg1.data
inputs.append(sim.gpr(reg1_sel).value)
reg2_ok = yield dec2.e.read_reg2.ok
if reg2_ok:
reg2_sel = yield dec2.e.read_reg2.data
inputs.append(sim.gpr(reg2_sel).value)
print(inputs)
if len(inputs) == 0:
yield alu.p.data_i.a.eq(0)
yield alu.p.data_i.b.eq(0)
if len(inputs) == 1:
yield alu.p.data_i.a.eq(inputs[0])
yield alu.p.data_i.b.eq(0)
if len(inputs) == 2:
yield alu.p.data_i.a.eq(inputs[0])
yield alu.p.data_i.b.eq(inputs[1])
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-11 16:13 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #41 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ok - *sigh* - we _could_ define it this way however if you look in
the decode1/2.vhdl you'll see that anton's team defined RS == RC.
(reg3_data).
https://github.com/antonblanchard/microwatt/blob/master/decode2.vhdl#L124
output reg is defined as RA and RT (yes we need a 2nd one)
https://github.com/antonblanchard/microwatt/blob/master/decode2.vhdl#L135
in this way i believe RB *always* ends up as "the register that
can be replaced by an immediate at the input side"
https://github.com/antonblanchard/microwatt/blob/master/decode2.vhdl#L79
you see what i mean?
so it's because reg positions are lost that RA suddenly receives reg data
that was supposed to be in RB
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-11 16:13 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #42 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #40)
> hmmm hmmm hang on hang on - this is removing the order. if there's 3 regs,
> then 3 regs are needed.
>
>
> what's needed is like this:
> <snip>...</snip>
> yield alu.p.data_i.a.eq(input[0][0]) # RA
> yield alu.p.data_i.b.eq(input[1][0]) # RB
> yield alu.p.data_i.c.eq(input[2][0]) # RC
>
I went through the tables and double checked, the *only* ALU instructions that
have 3 inputs are 2 registers and an immediate. It does not *need* 3 register
inputs.
However, some piece of hardware needs to order the inputs, I guess the trade
off is whether to do it in the alu or somewhere else.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
From: Lauri Kasanen @ 2020-05-11 17:34 UTC (permalink / raw)
To: libre-riscv-dev
Hi,
IBM has released the POWER10 ISA doc. It includes specifics on the
optional Power-compliant levels.
https://ibm.box.com/s/hhjfw0x0lrbtyzmiaffnbxh2fuo0fog0
Same, but wgettable, as the above only works in a browser:
https://ibm.box.com/shared/static/hhjfw0x0lrbtyzmiaffnbxh2fuo0fog0
- Lauri
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-05-11 17:52 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=307
Jock Tanner <tanner.of.kha@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tanner.of.kha@gmail.com
--- Comment #2 from Jock Tanner <tanner.of.kha@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #1)
> https://github.com/mozilla/kanbanzilla huge weird mixture of dependencies,
> nice
> concept, far too many dependencies (node, ruby, python - wtf??)
Only Python is a run-time dependency though. Node is needed once to build
browser JS, Ruby − for CSS.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-11 18:15 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #43 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #42)
> I went through the tables and double checked, the *only* ALU instructions
> that have 3 inputs are 2 registers and an immediate. It does not *need* 3
> register inputs.
yehyeh. ok.
really... normally, what would happen is that anything that's significantly
different like this would get put into its own Function Unit (into its own
ALU Pipeline).
then, there's no "switching about at the ALU side"
> However, some piece of hardware needs to order the inputs, I guess the trade
> off is whether to do it in the alu or somewhere else.
i think one of the reasons why processors go with a convention "B is
reg or immediate" is to save wires. you've got 64 bits worth of wires for
B, B is not used all the time, so when it's not, use it to farm in
the "immediate" data.
so i think we'll find... 1 sec let's look at the original decode2.vhdl...
ah yes:
https://github.com/antonblanchard/microwatt/blob/master/decode2.vhdl#L89
ok so that's definitely putting the *actual* immediate data into reg b.
decode_input_reg_b() is where the decision is made to either put the
regfile data into the return result or put the immediate in it.
so given that we're using microwatt's "decoder" we really need to
follow the same conventions. and here's where the execution has
*three* inputs:
https://github.com/antonblanchard/microwatt/blob/master/execute1.vhdl#L61
a_in, b_in, c_in.
so my feeling is we:
* have the ALU with the same 3 inputs (even though we know only 2 of them
are used), and keep the same order
* where the immediate is availabe assume it is always dropped into the b_in
64-bit wires
thus:
* remove the MUX from ALUInputStage (that means in the unit tests
it has to be done there)
with m.If(self.i.ctx.op.imm_data.imm_ok)
comb += self.o.b.eq(self.i.ctx.op.imm_data.imm)
with m.Else():
comb += self.o.b.eq(self.i.b)
so, in set_alu_inputs it would be:
inputs = []
# C (or A?)
reg3_ok = yield dec2.e.read_reg3.ok
reg3_sel = 0
if reg3_ok:
reg3_sel = yield dec2.e.read_reg3.data
reg3_sel = (sim.gpr(reg3_sel).value
inputs.append(reg3_sel, reg3_ok)
# B (or imm)
with m.If(self.i.ctx.op.imm_data.imm_ok)
reg2_sel = yield self.i.ctx.op.imm_data.imm)
with m.Else():
reg2_ok = yield dec2.e.read_reg2.ok
reg2_sel = 0
if reg2_ok:
reg2_sel = yield dec2.e.read_reg2.data
reg2_sel = (sim.gpr(reg2_sel).value
inputs.append(reg2_sel, reg2_ok)
# A (or C?)
and then still have 3 inputs, and in this way we save 64 bits
worth of wires because B is used to input the immediate.
one other key reason for doing it this way is because the FunctionUnit
front-end is where the decisions are made about reading from the
regfile (and acknowleding them). so it has to decode the Operand, there,
anyway, because it must not even send a *request* for Register B if
it does not actually need it.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-11 18:23 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #44 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
see this (yes it's LD/ST not an ALU)
https://libre-soc.org/3d_gpu/ld_st_comp_unit.jpg
you see how Op2 (RB) is selected through a mux, based on the Imm/Opcode?
the ALU (the weird "boat" symbol) doesn't get to make the decision, it
gets "told".
however if you follow the "imm_ok" wire from the Imm/Opcode latch, you'll
see it PREVENTS REQ_RD2 from even being activated, when "imm_ok" is true.
this is the primary purpose (role) of the Computation Units: make requests
for Register File Ports *that are needed*.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
From: Luke Kenneth Casson Leighton @ 2020-05-11 18:25 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200511203421.5d834abb14dbc2b7c979c6f7@gmx.com>
On Mon, May 11, 2020 at 6:33 PM Lauri Kasanen <cand@gmx.com> wrote:
>
> Hi,
>
> IBM has released the POWER10 ISA doc.
oo, major version-bump, ooo :)
> It includes specifics on the
> optional Power-compliant levels.
ahh thank you. which section / page number?
> https://ibm.box.com/s/hhjfw0x0lrbtyzmiaffnbxh2fuo0fog0
>
> Same, but wgettable, as the above only works in a browser:
> https://ibm.box.com/shared/static/hhjfw0x0lrbtyzmiaffnbxh2fuo0fog0
star
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
From: Luke Kenneth Casson Leighton @ 2020-05-11 18:28 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxPrGU_0UX6M1Aym8fjECfvTM1rg6jzEDK-_HfaWLtScw@mail.gmail.com>
ok found it, p9-10.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
From: Yehowshua @ 2020-05-11 18:31 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxPrGU_0UX6M1Aym8fjECfvTM1rg6jzEDK-_HfaWLtScw@mail.gmail.com>
> On May 11, 2020, at 2:25 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
>> IBM has released the POWER10 ISA doc.
OK - before we get confused on all this power non-sense any further - I’d like to stress that the ISA is currently committed at POWER3.0B.
POWER10 is an IBM processor family set to hit market 2021.
Why on earth IBM thought it was a good Idea to name a spec and implementation with conflicting numbers? Only God knows.
Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
From: Luke Kenneth Casson Leighton @ 2020-05-11 18:37 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <C00074CF-55D4-412C-976D-4F506B551FE6@gatech.edu>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Mon, May 11, 2020 at 7:31 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
>
>
> > On May 11, 2020, at 2:25 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> >
> >> IBM has released the POWER10 ISA doc.
>
> OK - before we get confused on all this power non-sense any further - I’d like to stress that the ISA is currently committed at POWER3.0B.
yehyeh. right now, to stand a chance to hit oct 2020, we've cut FP,
cut vector, cut regfile stratification - everything. absolute basic
processor.
> POWER10 is an IBM processor family set to hit market 2021.
>
> Why on earth IBM thought it was a good Idea to name a spec and implementation with conflicting numbers? Only God knows.
:)
we do however need to have the conversation with them, to plan ahead.
page xii (OpenPOWER Architecture Sandbox), i see where they're going...
"Developers are encour-aged to provide a means to disable custom extensions
to present an architecture that is supported by standard
system software and toolchain"
um... that's precisely what ISANS / ISAMUX is for!!
*smacks forehead*.
the language is nowhere near strong or clear enough. "encouraged" is
inadequate. it needs to be, "if you go one route, you follow these
procedures. if you go the other route you follow _these_ procedures"
Alain, Yehowshua: we need to talk with Hugh about this.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 70] evaluate Bus Architectures
From: bugzilla-daemon @ 2020-05-11 21:19 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-70-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=70
--- Comment #9 from Jacob Lifshay <programmerjake@gmail.com> ---
one interesting thing to investigate: can omnixtend run over wireguard? From my
initial research, ChaCha20 (one of the ciphers used) is implemented as a bunch
of binary adds, bitwise xors, and rotates, which seem quite easy to implement
in hardware assuming we only provide timing-attack resistance and *NOT*
power-attack resistance. The idea is that it would be resistant to attack over
the network and would use a well-tested protocol where we can use Linux's
network stack for testing purposes.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 70] evaluate Bus Architectures
From: bugzilla-daemon @ 2020-05-11 21:20 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-70-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=70
--- Comment #10 from Jacob Lifshay <programmerjake@gmail.com> ---
if we implemented omnixtend over wireguard, we would only need to implement
data packets in HW, relying on linux or some microcontroller to handle
connection keepalive, setup, teardown, etc.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] ppc-dev linux patch support for microwatt!
From: Luke Kenneth Casson Leighton @ 2020-05-11 22:19 UTC (permalink / raw)
To: Libre-RISCV General Development
https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-May/210525.html
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] ppc-dev linux patch support for microwatt!
From: Luke Kenneth Casson Leighton @ 2020-05-11 22:23 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDz=1aP9iekH_-e4r9yBXAquAYUBw0yyupQ98dP29ps_KQ@mail.gmail.com>
ahh :)
https://github.com/paulusmack/microwatt/blob/mmu/mmu.vhdl
On Mon, May 11, 2020 at 11:19 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-May/210525.html
>
> ---
> crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] ppc-dev linux patch support for microwatt!
From: Yehowshua @ 2020-05-11 22:23 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDz=1aP9iekH_-e4r9yBXAquAYUBw0yyupQ98dP29ps_KQ@mail.gmail.com>
> On May 11, 2020, at 6:19 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-May/210525.html
Either they're emulating an MMU or processes can corrupt one another…
Either way, looks like we have a Masochistic safe-plug solution for demo day if we we haven’t yet finished the hypervisor or MMU, and we wish to show more than micro python.
Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] ppc-dev linux patch support for microwatt!
From: Yehowshua @ 2020-05-11 22:27 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzZHD_NzaWLQ9vuMa2N7iA5=EanYqxpDp1h+WyM7+j2VQ@mail.gmail.com>
> On May 11, 2020, at 6:23 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> https://github.com/paulusmack/microwatt/blob/mmu/mmu.vhdl <https://github.com/paulusmack/microwatt/blob/mmu/mmu.vhdl>
Oh - its a fork. Haha
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] ppc-dev linux patch support for microwatt!
From: Luke Kenneth Casson Leighton @ 2020-05-11 22:34 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <D96DDBD2-461A-4CB9-B536-CC7434B97CA3@gatech.edu>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Mon, May 11, 2020 at 11:27 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
>
>
> > On May 11, 2020, at 6:23 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> >
> > https://github.com/paulusmack/microwatt/blob/mmu/mmu.vhdl <https://github.com/paulusmack/microwatt/blob/mmu/mmu.vhdl>
> Oh - its a fork. Haha
yes, paul mackerras is working on the RADIX MMU implementation, and
has got a linux kernel booting. that's really significant. i can do
a brain-dead conversion of his mmu.vhdl and associated data structures
in a couple of hours: i'm not so good at writing unit tests etc. that
takes longer: if we work together we should have a linux-capable MMU
in a few days.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
page: next prev latest
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git