Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* Re: [libre-riscv-dev] daily kan-ban update 28may2020
From: Alain D D Williams @ 2020-05-28 23:15 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyxRBy1DbnymncC5rP_vyDEFcquRFbqRjoCxor5bG_T0Q@mail.gmail.com>

On Fri, May 29, 2020 at 12:06:04AM +0100, Luke Kenneth Casson Leighton wrote:
> On Fri, May 29, 2020 at 12:02 AM Alain D D Williams <addw@phcomp.co.uk> wrote:
> 
> > A virtual Debian 10 - oh, good looks as if it will work ... just need a few new
> > packages .... damn ! RFS out of space; so move & symlink.
> 
> ah yes sorry, latex does historically come with a hell of a lot of
> packages.  if you apt-get clean (or rm /var/lib/apt/cache/*.deb) you
> should get 300mb back, at least.

The VM was more to play with the latest debian than do real work ... I just
installed not really worrying about how it partitioned the disk. It gave RFS
5.5 GB. Thanks to whoever working on BSD invented the symbolic link!

-- 
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256  https://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html
#include <std_disclaimer.h>

_______________________________________________
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 353] formal proof of soc.regfile classes RegFile and RegFileArray needed
From: bugzilla-daemon @ 2020-05-28 23:18 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-353-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=353

--- Comment #21 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #20)
> (In reply to Cole Poirier from comment #18)
> > (In reply to Luke Kenneth Casson Leighton from comment #13)
> > > i suggest starting with two utterly different proofs, divided and isolated
> > > with "if self.writethru".  yes NOT m.If because python parameters != nmigen
> > > AST.A
> > > 
> > > then, to do a 4 way (dual nested) set of m.If on ren and wen.
> > > 
> > > then, in EACH quadrant, do completely separate assertions.
> > > 
> > > but before making those assertions, write out in words the expected
> > > behaviour when the 4 way truth table of wen and ren occurs.
> > 
> > I think I might not understand the functionality of the module enough to
> > know the expected behaviour. Is it the case that if not writethru nothing is
> > supposed to happen?
> > 
> > Further with regard to Michael's comments about needing to use Initial() and
> > ResetSignal() should I wrap the if writethru..else in a "with
> > m.If(init)...with m.Else()" similar to proof_fu.py?
> 
> yyep.
> 
> > Is it the case that, if
> > Initial() then do rd operations, and else do wr operations?
> 
> nnope.  Initial() is just that: the initial conditions.
> 
>  
> > Finally, with regard to the 4-way truth table, is this format close to
> > correct?
> > 
> > ```
> > rd.ren wr.wen rd.data_o reg
> > 0      0      x         y
> > 0      1      x         y
> > 1      0      x         y
> > 1      1      x         y
> > ```
> 
> yep.  drop that into a comment in the code, so we can edit it before
> implementing it.

Ok. Pushed a commit with that. Can you take a look?

-- 
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 28may2020
From: Cole Poirier @ 2020-05-28 23:32 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <36FA381D-E344-4158-80AE-70BD90962B7F@gatech.edu>

On May 28 2020, at 4:09 pm, Yehowshua <yimmanuel3@gatech.edu> wrote:
> Today:
>  
> Finished a website with strikingly similar objectives to Libre-SOC.
> Could it be?
> Nah…
>  
> https://systemeslibres.org <https://systemeslibres.org/>

Very, very, very cool!! Two quick notes, under the section "When can I
get a chip?" it says "Fall 2021 A single core Libre-SOC with a GPU and
open should be market ready by fall 2021." Which word has been
accidentally left out after open? Also on your updates the date is being
left out for some reason so it simply reads "Tuesday, May, 2020".  

Cole

_______________________________________________
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 353] formal proof of soc.regfile classes RegFile and RegFileArray needed
From: bugzilla-daemon @ 2020-05-28 23:41 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-353-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=353

--- Comment #22 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #21)

> Ok. Pushed a commit with that. Can you take a look?

done.  updated.  basically, this is... complicated.  there's time-dependent
interactions.  i actually managed to get one case to work: when wen is
not set, the reg should not change.  past value should equal the present value.

-- 
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 28may2020
From: Luke Kenneth Casson Leighton @ 2020-05-28 23:47 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <7C3E5B04-0D7C-4FC7-B948-486357F4FA5D@getmailspring.com>

https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fsystemeslibres.org

strange: this isn't completing, it sits at 99%.  does anyone else have
better luck?

l.

On Fri, May 29, 2020 at 12:32 AM Cole Poirier <colepoirier@gmail.com> wrote:
>
> On May 28 2020, at 4:09 pm, Yehowshua <yimmanuel3@gatech.edu> wrote:
> > Today:
> >
> > Finished a website with strikingly similar objectives to Libre-SOC.
> > Could it be?
> > Nah…
> >
> > https://systemeslibres.org <https://systemeslibres.org/>
>
> Very, very, very cool!! Two quick notes, under the section "When can I
> get a chip?" it says "Fall 2021 A single core Libre-SOC with a GPU and
> open should be market ready by fall 2021." Which word has been
> accidentally left out after open? Also on your updates the date is being
> left out for some reason so it simply reads "Tuesday, May, 2020".
>
> Cole
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

_______________________________________________
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 28may2020
From: Cole Poirier @ 2020-05-28 23:53 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDyvAkwGuGPg1CLoN3AejSHbgNu5qwo=fnpEEH4n9LW1FQ@mail.gmail.com>

On May 28 2020, at 4:47 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fsystemeslibres.org
> 
> strange: this isn't completing, it sits at 99%.  does anyone else have
> better luck?
> 
> l.

Yes, just ran on my iphone 8 got 93/100. 2.7s largest contentful paint,
4.6s time to interactive.

Cole

_______________________________________________
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 353] formal proof of soc.regfile classes RegFile and RegFileArray needed
From: bugzilla-daemon @ 2020-05-28 23:57 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-353-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=353

--- Comment #23 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #22)

> done.  updated.  basically, this is... complicated.  there's time-dependent
> interactions.  i actually managed to get one case to work: when wen is
> not set, the reg should not change.  past value should equal the present
> value.

Ah it's time-dependent, that makes sense. Thanks, pulled and ran the test.
Cool. How would I go about better understanding how ren and wen are supposed to
interact? Studying the logic diagram? Or something 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] Rough Architectural Sketch
From: Yehowshua @ 2020-05-29  1:58 UTC (permalink / raw)
  To: Libre-RISCV General Development

Hey Luke,

Can you get me a rough hand-drawn picture of the the CPU architecture?
Something with the scoreboard with arrows to the functional units. I’ll draw it up
In the FOSS draw.io <http://draw.io/> diagram generator.

Something representative of October’s/November’s tapeout target.
The functional units can just be boxes. The level of appropriate accuracy
would include the right number of functional units.

Is this something that can be done in 30ish minutes on your end?

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] Rough Architectural Sketch
From: Luke Kenneth Casson Leighton @ 2020-05-29  2:45 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <258716B0-5FFA-4E47-A5A8-71652E7C59E0@gatech.edu>

On Friday, May 29, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

> Hey Luke,
>
> Can you get me a rough hand-drawn picture of the the CPU architecture?
> Something with the scoreboard with arrows to the functional units. I’ll
> draw it up
> In the FOSS draw.io <http://draw.io/> diagram generator.
>
> Something representative of October’s/November’s tapeout target.
> The functional units can just be boxes. The level of appropriate accuracy
> would include the right number of functional units.


at this broad level t's actually not that differemt from what is in mitch's
1st book chapter.

345am now. more tomorrow



>
> Is this something that can be done in 30ish minutes on your end?
>
> Yehowshua
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
>


-- 
---
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] Debug port (was Re: minimum viable ASIC)
From: Luke Kenneth Casson Leighton @ 2020-05-29 10:30 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxRMyVdga44mJ6GL+jOHxAz=DrwqFJEB013Eh3rVqCb6A@mail.gmail.com>

On Wednesday, May 20, 2020, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

import nmigen as nm
> x = nm.Signal()
>
> is actually a really good idea.  saves space, explicitly says where
> the "thing" (Signal etc.) come from.


i found some code where we do just module import:

https://git.libre-soc.org/?p=nmutil.git;a=blob;f=src/nmutil/singlepipe.py;h=cbd06f648b23a3ad6e9b064093de0f039c76bb32;hb=HEAD#l877

similar to "import operator" or "import math" then use

math.pi
math.cos(x)
operator.add

etc.

this is very good practice, Staf, because it allows the reader, at the
point of use of the function or class, to know immediately without
scrolling to the top of the page, which module the code comes from.

whilst *you* might know that, other readers will not.  the additional
context is critical for *their* understanding and to not force them to work
harder, slowing them down to the point where mistakes are made or they give
up and find someone else's code.

bottom line: it's not about you :) these are practices that make life
easier for *other people*.

l.




-- 
---
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

* [libre-riscv-dev] daily kan-ban update 29may2020
From: Luke Kenneth Casson Leighton @ 2020-05-29 12:04 UTC (permalink / raw)
  To: Libre-RISCV General Development

yesterday:

* continued review/assistance Tobias DataMerger
* continued guess-work on regfile formal proof
* started a compunit variant of test_pipe_caller for ALU.  discovered
that MultiCompUnit is not pipeline-compliant.

today:

* continue investigating non-compliance with pipeline API.  Cesar:
this *does not* affect what you are doing.

l.


---
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

* [libre-riscv-dev] [Bug 310] Function Units to cover multiple tasks
From: bugzilla-daemon @ 2020-05-29 13:42 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-310-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=310

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
a good one to try here is to add logical AND/OR/XOR to the
*ALU* pipeline.  this should be very simple however it is
the unit tests (and formal correctness proof) that will
need most alteration

these:

https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/logical/main_stage.py;hb=HEAD#l49

to be added here:

https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/alu/main_stage.py;hb=HEAD#l58

-- 
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 357] New: create simplified (testing) version of Function Unit pipeline for test purposes
From: bugzilla-daemon @ 2020-05-29 13:49 UTC (permalink / raw)
  To: libre-riscv-dev

https://bugs.libre-soc.org/show_bug.cgi?id=357

            Bug ID: 357
           Summary: create simplified (testing) version of Function Unit
                    pipeline for test purposes
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Source Code
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

a simplified version of a Function Unit pipeline is needed which has
the same functionality as soc.experiment.alu_hier.ALU but has the
soc.fu front-end API (including regspec compliance).

take this code (particularly main_stage.py):
https://git.libre-soc.org/?p=soc.git;a=tree;f=src/soc/fu/alu;hb=HEAD

and cut it *right* back so that it has the same functionality as this:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/experiment/alu_hier.py;h=bebe6468cc78975e0e98794fe8d5f72321eb0d50;hb=HEAD#l195

but without the mess of the actual ALU side being mixed in with
the pipeline handling.

-- 
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 29may2020
From: Yehowshua @ 2020-05-29 13:51 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyRcO_eXcP04H+WyoQ10e8mie7NivGJtyW8D06YOMQsnQ@mail.gmail.com>

Today:

Going to take a stab at one of the applications NLNet sent us for future grants.

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

* [libre-riscv-dev] [Bug 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-05-29 13:56 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=216

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=263

-- 
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 263] LD/ST batching needed
From: bugzilla-daemon @ 2020-05-29 13:56 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-263-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=263

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=216

-- 
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 29may2020
From: Luke Kenneth Casson Leighton @ 2020-05-29 14:14 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <BCFACE12-0D58-4B1E-ACC3-3AF46BFEF54F@gatech.edu>

On Fri, May 29, 2020 at 2:51 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> Today:
>
> Going to take a stab at one of the applications NLNet sent us for future grants.

great.  can i suggest using the wiki -
https://libre-soc.org/nlnet_proposals/ - so that there is full
transparency, and also so that everyone can participate in reviewing
and writing the application?

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] daily kan-ban update 29may2020
From: Yehowshua @ 2020-05-29 14:21 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyvOURmCnnc6rC79J7QkJVCfND7DwVEhOSMm2jETEpCpQ@mail.gmail.com>

> 
> great.  can i suggest using the wiki -
> https://libre-soc.org/nlnet_proposals/ - so that there is full
> transparency, and also so that everyone can participate in reviewing
> and writing the application?
> 

Absolutely.

> l.
> 
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev


_______________________________________________
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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-05-29 16:17 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=216

--- Comment #52 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
tobias: the DataMerger class is coming along well.  now that the unit
test passes (doesn't break anything) feel free to enable it by default,
and then use it to confirm, incrementally, from that point on, that
what you commit will now at least "not break anything" :)

btw do give each DataMergerRecord() a unique name.  this so that when
people inspect the graphviz, each DataMergerRecord will have a prefix
{name}_data etc. by which they can be identified correctly with the
python source code.

next bit: unit test.  after that: formal proof.

-- 
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 29may2020
From: Cesar Strauss @ 2020-05-29 16:51 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDyRcO_eXcP04H+WyoQ10e8mie7NivGJtyW8D06YOMQsnQ@mail.gmail.com>

Going along nicely, if slowly, with the parallel unit test of
src/soc/experiment/compalu_multi.py. Thankfully, the weekend is near, so
I expect to finally finish this task, and move along the queue.

Got a nice unplanned example of a race condition when, surprisingly,
running the test twice in a row passed, then failed, without changing
anything. Hint: when passing information from one co-routine to another,
do it around a synchronization point / barrier.

Also, learned how to use Settle() to respond asynchronously to outputs
of the DUT. It's useful for simulating a zero-delay response to a
request, or a purely combinatorial ALU.

Overall, I am quite enjoying the exercise.

Regards,

Cesar

_______________________________________________
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 29may2020
From: Luke Kenneth Casson Leighton @ 2020-05-29 17:27 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <dfb0cc93-009c-6e2d-d868-4d88a46824ed@gmail.com>

On Friday, May 29, 2020, Cesar Strauss <cestrauss@gmail.com> wrote:

> Going along nicely, if slowly, with the parallel unit test of
> src/soc/experiment/compalu_multi.py. Thankfully, the weekend is near, so
> I expect to finally finish this task, and move along the queue.
>
> Got a nice unplanned example of a race condition when, surprisingly,
> running the test twice in a row passed, then failed, without changing
> anything. Hint: when passing information from one co-routine to another,
> do it around a synchronization point / barrier.


yyep.

now you know why i put, in the TODO comments, to first wait for busy being
LOW in a loop, then for busy HI in a loop, and *then* proceed.




> Also, learned how to use Settle() to respond asynchronously to outputs
> of the DUT. It's useful for simulating a zero-delay response to a
> request, or a purely combinatorial ALU.


oh.  nice.  i will experiment with that.  i can think of several places i
should have used it.


> Overall, I am quite enjoying the exercise.


:)


>
> Regards,
>
> Cesar
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
>


-- 
---
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] daily kan-ban update 29may2020
From: Jacob Lifshay @ 2020-05-29 23:19 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyRcO_eXcP04H+WyoQ10e8mie7NivGJtyW8D06YOMQsnQ@mail.gmail.com>

today: working on div and mul pipelines

probably won't get a lot done due to helping my friend build his computer
after finally getting the right motherboard. spent several hours only to
discover that the new mobo is defective.

Jacob
_______________________________________________
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 29may2020
From: Luke Kenneth Casson Leighton @ 2020-05-29 23:55 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4rGKGYb46iN3D6Ovkrom4inoy+ekEidCsppJyYK-HyCQ@mail.gmail.com>

---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

On Sat, May 30, 2020 at 12:20 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> today: working on div and mul pipelines

cool.

> probably won't get a lot done due to helping my friend build his computer
> after finally getting the right motherboard. spent several hours only to
> discover that the new mobo is defective.

aiyaaa :)  i hate it when that happens.  i've built... over... 20
systems in the past (including a 386, back in.... 1992-3 i think,
where i saved money by putting it into a small cardboard box).  i've
always been lucky that they always worked - except for those 8 systems
that had memory faults that needed a BIOS update.

good luck :)

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] daily kan-ban update 29may2020
From: Luke Kenneth Casson Leighton @ 2020-05-29 23:58 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <dfb0cc93-009c-6e2d-d868-4d88a46824ed@gmail.com>

On Fri, May 29, 2020 at 5:52 PM Cesar Strauss <cestrauss@gmail.com> wrote:

> Also, learned how to use Settle() to respond asynchronously to outputs
> of the DUT. It's useful for simulating a zero-delay response to a
> request, or a purely combinatorial ALU.

i can confirm: it does as intended.

https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=cf573b0dfd3cb3f69dc28a162109dd92b0da72fd

so thank you for bringing that to everyone's attention, Cesar.  i was
previously writing tests that waited an entire cycle - as if they were
synchronous - and wondering what the hell was going on.

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] EU residency / businesses
From: Luke Kenneth Casson Leighton @ 2020-05-30  9:58 UTC (permalink / raw)
  To: Libre-RISCV General Development

https://e-resident.gov.ee/start-a-company/
https://e-resident.gov.ee/become-an-e-resident/
https://yourcompanyinestonia.com/how-to-register-your-company-in-estonia-step-by-step/

we need to have an EU "business" presence, if we are to apply for EU
funding such as this:
https://essif-lab.eu/?page_id=134

a way to achieve that is to apply for Estonian E-residency, and
establish a business online, there.  by making sure that Estonia
directly financially benefits, the country is happy to put a sovereign
stamp on things.

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:   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