Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* Re: [libre-riscv-dev] daily kan-ban update 06may2020
From: Luke Kenneth Casson Leighton @ 2020-05-06 16:30 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <d3063996-e91e-9f30-ce3a-496c5e8a27ae@gmail.com>

On Wed, May 6, 2020 at 5:23 PM Michael Nolan <mtnolan2640@gmail.com> wrote:

> I'm not sure how to fix this aside from having the code generator
> surround every comparison expression with SelectableInt(x, bits=1)

it'll look awful however that's a perfectly reasonable solution - go
for it.  i'm amazed the auto-generated output is as readable as it is.

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 06may2020
From: Michael Nolan @ 2020-05-06 16:23 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDyRnFhaT5tADj6ka+=Qo1RKUZjeafO9x8iFdGvXavy5yA@mail.gmail.com>

Working on branches in the power_pseudo simulator. I now have branch and 
link working, move to spr, and branch to lr and ctr working. I did run 
into an issue here though, in that the generated python is slightly 
broken in a way I'm not entirely sure I can fix inside the code 
generator. I added a way to automatically patch the generated python 
files to work around this.

The issue is in the following line:

         ctr_ok = BO[2] | (CTR[M:64] != 0) ^ BO[3]

It xors the result of comparing CTR to 0 (which is a bool) with BO[3] 
(Which is a selectableInt)
I'm not sure how to fix this aside from having the code generator 
surround every comparison expression with SelectableInt(x, bits=1)

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

* Re: [libre-riscv-dev] daily kan-ban update 06may2020
From: Luke Kenneth Casson Leighton @ 2020-05-06 14:58 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <20200506153134.bccaf1dc7312400d7ec1ba81@platen-software.de>

On Wed, May 6, 2020 at 2:31 PM Tobias Platen
<libre-soc@platen-software.de> wrote:

> On Wed, 6 May 2020 10:37:50 +0100
> Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> I will be working on the simulator until Friday, integer ops that change the condition register.

oh good.  we need that.

> The update_cr0 method in the InternalOpSimulator is partially implemented, currently one bit is not set yet.

ok, good to know - not a problem.  remember that if you're the only
person using some code (because it's entirely new), you can't do any
"harm" to the rest of the codebase, so commit regularly, do *not* wait
"a few days until it's totally finished".

then people who need to coordinate around what you're doing can do so,
because they see the regular commits in certain files.

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 06may2020
From: Luke Kenneth Casson Leighton @ 2020-05-06 14:55 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <E271FE67-6059-4F08-BF9E-7159598F8755@gatech.edu>

On Wed, May 6, 2020 at 3:00 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> Still doing the legal work..

great.

> Made an attempt to explain how PowerOP combined with Enum works…
>
> https://libre-soc.org/Documentation/SOC/index/ <https://libre-soc.org/Documentation/SOC/index/>

PowerOp....
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/decoder/power_decoder.py;h=6094da1b4c84cbe1e1342cda62733bd3e1db6774;hb=HEAD#l106

ah that one mirrors what's in the CSV files, basically (where in
microwatt it was all hard-coded into the VHDL files).

it's directly equivalent to decode_rom_t type in microwatt:
https://github.com/antonblanchard/microwatt/blob/master/decode1.vhdl#L33

which you can then see in decode_types:
https://github.com/antonblanchard/microwatt/blob/master/decode_types.vhdl#L50

note that PowerOp is an *internal* type.  you would never actually use
or interface directily with PowerOp.  the "end-user" would use
PowerDecode2.
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/decoder/power_decoder2.py;h=4a3785efaba9c03d76a0159f19e4cab0219d0b7d;hb=HEAD#l329

as that contains *all* decoded fields (merged globally into the one
data structure regardless of whether they are needed), this is quite
annoying, so there are two *SUBSET* classes that "pinch" only the
fields that are needed (and there will be more of those).

ComputationUnit's Decode subset, ComALUOpSubset:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/experiment/alu_hier.py;h=0021c0793c6cf874060148ff83c0cee6720b6f8d;hb=HEAD#l23

and the LDSTCompUnit's Decode subset, CompLDSTOpSubset:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/experiment/compldst_multi.py;h=d1be1355ecce4f8e1b503c0b950a46ad306ae1f4;hb=HEAD#l66

note how CompLDSTOpSubset, CompALUOpSubset and Decode2Execute1Type all
derive from nmigen Record.  this provides "fields" (which comes from
the layout) which in turn allows us to walk through the Record and
grab only the subset of fields that we actually want to copy.

the "normal" Record.eq would unfortunately treat the *BITS* of each
derived Record as "a fixed sequential linear block of bits to copy"
(treating the two exactly like memcpy).

can i leave it with you to update the source code docstrings with
notes from the above?  if not, let me know and i'll do it.

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 06may2020
From: Yehowshua @ 2020-05-06 13:59 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyRnFhaT5tADj6ka+=Qo1RKUZjeafO9x8iFdGvXavy5yA@mail.gmail.com>

Still doing the legal work..

Made an attempt to explain how PowerOP combined with Enum works…

https://libre-soc.org/Documentation/SOC/index/ <https://libre-soc.org/Documentation/SOC/index/>

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] daily kan-ban update 06may2020
From: Tobias Platen @ 2020-05-06 13:31 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDyRnFhaT5tADj6ka+=Qo1RKUZjeafO9x8iFdGvXavy5yA@mail.gmail.com>

On Wed, 6 May 2020 10:37:50 +0100
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

I will be working on the simulator until Friday, integer ops that change the condition register.
The update_cr0 method in the InternalOpSimulator is partially implemented, currently one bit is not set yet.

Tobias


> i will continue working on the multi-go/req new version of LDSTCompUnit.
> got 30% through it yesterday.
> 
> talked with marketnext. marketnext have done a fantastic video for us, for
> their hackathon. they set a deadline of mar 15th for applicants.
> 
> 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


-- 
Tobias Platen <libre-soc[at]platen-software[dot]de>

_______________________________________________
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-06 13:12 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=302

-- 
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 302] create a list of exception types for LD/ST operations in POWER
From: bugzilla-daemon @ 2020-05-06 13:12 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-302-13@https.bugs.libre-soc.org/>

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

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

* [libre-riscv-dev] [Bug 302] New: create a list of exception types for LD/ST operations in POWER
From: bugzilla-daemon @ 2020-05-06 13:02 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 302
           Summary: create a list of exception types for LD/ST operations
                    in POWER
           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: ---

we need a list of exceptions and a suitable enum / data-type created
for them.

-- 
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 status update 05may2020
From: Luke Kenneth Casson Leighton @ 2020-05-06 13:00 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzs-aHLh3pcwTRKefdcup7dm3caSuBVu_gBN9BLD=7+Jg@mail.gmail.com>

On Wed, May 6, 2020 at 10:34 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:

>> I mentioned that our project extensively uses reset_less=True with
>> combinatorial signals on the now-closed nmigen bug about adding
>> warnings for that case:
>> https://github.com/nmigen/nmigen/issues/379
>
>
> there is a resetless domain.

... which probably wouldn't have helped.

thank you for taking care of that: it would have been a royal pain in
the neck to suddenly have thousands of unnecessary warnings.

btw as an example, the CompUnits have an explicit "reset" capability -
a line named "go_die".  when that's asserted, the SR Latches reset
back to "known-good".  to have a "hidden nice convenient reset line"
to every single synchronous signal would be a huge waste of resources.
likewise the Dependency Matrices have a similar thing.

nice reset is great for FPGAs.  it's also useful for interface code,
to get it back into a known-good state.

we *do* use reset - i think - in the pipeline register-latch API,
because that's a place where it's needed.  although, there, again, for
"mask cancellable" pipelines we do *not* need "reset"... because
pulling the mask-cancel bit *does that exact same job*.

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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-05-06 12:39 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 #38 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=65a2218914d3f9a82d161c4cb946e5332d49b666

i've added a TODO class "DualPortSplitter" - actually it should
probably kinda be that LDSTSplitter should be adapted to conform
to PortInterface.

can you do that task, jacob? it's a simple self-contained task that's
an important step - no need to examine any of the other code.

-- 
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] global network of developers
From: Luke Kenneth Casson Leighton @ 2020-05-06 10:47 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <624E1265-0D56-4A9E-8BA2-6F91AD72EDC2@gatech.edu>

https://www.youtube.com/watch?v=Px6eakWja3Q

do share widely.  in particular in emerging markets.

_______________________________________________
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 208] implement CORDIC in a general way sufficient to do transcendentals
From: bugzilla-daemon @ 2020-05-06  9:53 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-208-13@https.bugs.libre-soc.org/>

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

--- Comment #55 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #54)

> > if you can drop that into a repository, get it working, write a
> > few simple experiments and see how it operates in each of the 6
> > modes, we're on a roll :)
> 
> I can give it a whirl I suppose

when you have a moment, i noticed that the two functions are actually
incredibly similar.  line-by-line it is a multiply or add, here or there.


btw i saw the commit putting ctx back in.  to test that, cookie-cut
FPADDMuxInOut in fpadd/pipeline.py and fpadd/test/test_fpadd_pipe.py

the ReservationStations class takes two parameters: the bitwidth
and the *number of Function Units*.  it uses ctx to drop the FU number
in along the pipeline, and on the output it uses that FU number to
*re-associate* the result with the correct Function Unit.

runfp knows exactly how ReservationStations works, so there is no need to
write any actual unit test infrastructure.

there is a single-argument version of runfp (i think!) so... oh wait,
you call runfp with "singleop=True".

then instead of passing in "add" as a function to compute the unit
test result, you pass in "math.cos".

that will throw a massive suite of corner-cases at the pipeline, so
be prepared for it to fail as we still have to do INF, NAN, 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] daily kan-ban update 06may2020
From: Luke Kenneth Casson Leighton @ 2020-05-06  9:37 UTC (permalink / raw)
  To: Libre-RISCV General Development

i will continue working on the multi-go/req new version of LDSTCompUnit.
got 30% through it yesterday.

talked with marketnext. marketnext have done a fantastic video for us, for
their hackathon. they set a deadline of mar 15th for applicants.

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

* Re: [libre-riscv-dev] daily status update 05may2020
From: Luke Kenneth Casson Leighton @ 2020-05-06  9:34 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6tdw0y9D5R-eaoSjVBGovpRM1yMqL3KJs5z5XdKnizvA@mail.gmail.com>

On Wednesday, May 6, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:

> On Tue, May 5, 2020 at 3:48 AM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
> > that's it.  what is everyone else doing?
>
> I saw the phoronix article that the wayland book is now freely
> available, so I ended up reading it since it will be useful for
> implementing wayland support in Kazan later.
> https://www.phoronix.com/scan.php?page=news_item&px=Wayland-Book-Free


nice.


>
> I mentioned that our project extensively uses reset_less=True with
> combinatorial signals on the now-closed nmigen bug about adding
> warnings for that case:
> https://github.com/nmigen/nmigen/issues/379


there is a resetless domain.



>
> I ended up adding the DEFERRED status to the bugzilla installation,
> since that way bugs will still show up in the lists of open bugs but
> it's obvious from a glance that we aren't worrying about them right
> now.


ok good idea


>
> I'm in the midst of figuring out the load/store code Luke wrote, so
> you may not see much activity right away.


ok.

do ask questions.  incremental approach.  questions is activity and is
perfectly fine.

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

* Re: [libre-riscv-dev] Finished Scoreboard
From: Luke Kenneth Casson Leighton @ 2020-05-06  9:08 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <690DF9FB-783E-49DB-9D86-0233D34F57B8@gatech.edu>

On Tuesday, May 5, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

> Well I’d like to be realistic. I’ve done large RTL projects before - if
> the scoreboard isn’t ready to do by June, we may have to look into the
> minimum viable product for October. Having a multi cycle non-pipelined CPU
> is way better than no CPU.


 NLNet money is only available for the defined set task.  No GPU, no money.

that means that alternative designs will need to find other sources of
funds.


> Luke, given only you have the knowledge to do the Scoreboard at the
> moment, it’d be wise to put eggs in more than one basket. Also, it takes at
> least a semester to fully comprehend the scoreboard architecture, so we
> can’t just add people to help you.


ancillary tasks.

>
> Just some things to keep in mind.
>
> 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] Finished Scoreboard
From: Luke Kenneth Casson Leighton @ 2020-05-06  9:06 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <BL0PR07MB3908C2967A9FD433206C93FDECA70@BL0PR07MB3908.namprd07.prod.outlook.com>

On Tuesday, May 5, 2020, Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:

> Maybe we could say finished by Mid-June -


yes.


>
>  but more than that would really be pushing things I think.


yes.




-- 
---
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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-05-06  8:42 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 #37 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #34)
> What do you think of the idea to write a single-op-at-a-time memory
> interface with all the caches & stuff to work with the rest of the SoC?

as intermediary steps this is a good idea.   the code i wrote yesterday already
does exactly that (and is why i did it. it "works". performance sucks.)

however stopping at a level that does not meet the requirements of keeping
those twin 128 bit L1 caches fully occupied on every cycle is not.



> it will be much simpler to get right and not take as much time, then, after
> that works, we can work on the much more complex multi-op version. That way,
> we will have something that works even if the multi-op version doesn't end
> up working in time for the october tape out.

yes.

although it will suck.

strictly speaking just as in minerva if you look at the code there exists
"cache bypassed" LoadStore code.

by using that code directly we also have the option to switch off the L1 cache,
making unit testing much easier.

and to emphasise, again (i have mentioned this about four times but have not
received a response), the minerva L1 code and associates LDST compiletime
reconfigureable Interface does *not* need duplicating.  it is good enough as-is
and can simply be expanded to 64 bit then quqdrupled up, or expanded to 128 bit
and doubled up, and 128 to 64 bit Wishbone Arbiters dropped on the front.

with only needing to connect to two well defined interfaces (multiple
PortInterfaces on one side and multiple minerva LDSTCache interfaces on the
other) this task is much simpler and straightforward than it seems.

-- 
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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-05-06  8:29 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 #36 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #35)
> The proposed single-op-at-a-time interface would work through PortInterface,
> since you already wrote a lot of the code needed to work with it.

the code i wrote is sufficient to get me to the point where i can test
LDSTCompUnit.

it already does exactly what you propose.

as a concept, it is "technically correct" and would actually "not corrupt
memory"

however it will have performance that is, ultimately, a waste of effort.

adding dual 128 bit memory interfaces would be 10% utilised, because they would
receive only one 8-64 bit request.

we might as well just use minerva's L1 code directly, in full, only one
interface 
 with the only change being to expand it to 64 bit from 32.

in addition, misaligned requests would not 
be handlee at the hardware level, leaving us non-compliant with the POWER spec.

bottom line is that the current code is for testing purposes and prototyping. 
its usefulness in particular is as a "mock test" i.e. to ensure that a single
LDSTCompUnit "works" and that is why i wrote it, *not* to actually put it into
a production chip.

it can in no way be used to *properly* test the parallel capability of the
engine because it will only do one request at a time.

if we want to be taken seriously and want the performance of a GPU we need the
twin buffer implemented in the next week.

i will have the LDSTCompUnit done by then and we will need to begin testing of
parallel LD/STs.

-- 
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] website title
From: Luke Kenneth Casson Leighton @ 2020-05-06  7:22 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4bTq+6Drx49pQp3cOzU10ht6szcd=RxGpx3neK26TtUA@mail.gmail.com>

On Wednesday, May 6, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:

> I noticed the title for the wiki is still libreriscv, we should change it
> to Libre-SOC.


i wonder why.  might be from the repo name?



-- 
---
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] crowdsupply update progress
From: Luke Kenneth Casson Leighton @ 2020-05-06  6:58 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4D0hfK7BORtcrKYyusi05fTT-6fKeut8K_+u9wFU2F0g@mail.gmail.com>

On Wednesday, May 6, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:

>
> send another email? If that doesn't work, send one to someone else at
> crowdsupply?


i sent one yesterday, covering the EOMA68 project.  still no response.

they have a ticket system, he's just... overloaded.

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

* Re: [libre-riscv-dev] crowdsupply update progress
From: Jacob Lifshay @ 2020-05-06  6:46 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxDAqoKtwj7hCagXjhrKAcUUAiiVWo3YP1ereh0Egyccw@mail.gmail.com>

On Tue, May 5, 2020, 23:44 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Wednesday, May 6, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > we still haven't released the crowdsupply update,
>
>
> joshua hasn't got back to me about it yet.
>

send another email? If that doesn't work, send one to someone else at
crowdsupply?

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] crowdsupply update progress
From: Luke Kenneth Casson Leighton @ 2020-05-06  6:44 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD62SFsE2VCJT70Rvw0rN0=tkq4wwgVJB2=DDTojVvdRQA@mail.gmail.com>

On Wednesday, May 6, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:

> we still haven't released the crowdsupply update,


joshua hasn't got back to me about it yet.


>  what's our progress?


dependent on joshua responding.

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] crowdsupply update progress
From: Jacob Lifshay @ 2020-05-06  6:07 UTC (permalink / raw)
  To: Libre-RISCV General Development

we still haven't released the crowdsupply update, what's our progress?

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

* [libre-riscv-dev] website title
From: Jacob Lifshay @ 2020-05-06  5:40 UTC (permalink / raw)
  To: Libre-RISCV General Development

I noticed the title for the wiki is still libreriscv, we should change it
to Libre-SOC.

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

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