* Re: [libre-riscv-dev] Contributing to the Libre-Soc Project
From: Yehowshua @ 2020-06-06 23:03 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAE_rhwZK4FeFHDh4SNiUozji1vR1L4Xm=+BVBRuxHMw49CsMhQ@mail.gmail.com>
> On Jun 6, 2020, at 6:29 PM, Sanjay Menon <sanjayamenon.mec@gmail.com> wrote:
>
> Hi,
>
> I am a budding VLSI enthusiast and open-source developer. I would love to
> work with the team in your goal to achieve a completely open source project.
>
My response will be quick as I spend my weekends writing my Master’s
Thesis.
Hi. And fantastic. We have a charter, that you should review here:
https://libre-soc.org/charter/ <https://libre-soc.org/charter/>
> I believe that as a beginner in this area, I would be able to learn more
> from you guys as I contribute to this wonderful project.
Sure. Would probably start by learning nMigen as it seems you’re coming
from a verilog background.
https://github.com/RobertBaruch/nmigen-tutorial <https://github.com/RobertBaruch/nmigen-tutorial>
http://blog.lambdaconcept.com/doku.php?id=nmigen:tutorial <http://blog.lambdaconcept.com/doku.php?id=nmigen:tutorial>
At the moment, we’re prepping for the Oct/Nov 2020 Tapeout.
Most of the work is going into hooking up the scoreboard to
our functional units right now.
We also make extensive use of formal verification.
Which reminds me, we need to separate FHDLTestCase class
into the nmutils repo since it's no longer officially maintained.
That’s a pretty simple task - maybe something you could handle.
You’ll know what I mean once you start playing with nMigen.
We also should start putting test we want to in `__init__.py` in the soc/tests
folder - so that `setup.py test` works.
So much to do, the aforementioned tasks are pretty beginner level.
>
> I thank Yehowshua Immanuel for introducing me to this project. Can't wait
> to start already. Hoping to hear from you soon.
>
> To know more about me do checkout my LinkedIn
> <http://www.linkedin.com/in/sanjay-menon-91791815a> profile.
>
> Thanks and regards,
> Sanjay A Menon
Welcome,
Yehowshua
> _______________________________________________
> 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] Introduction and Questions
From: Luke Kenneth Casson Leighton @ 2020-06-06 22:48 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <D56B0575-0D6D-40F1-BA88-C0B689B9A55D@gatech.edu>
yes, apologies! (hi jeremy, btw the discussion we had was genuinely
appreciated).
l.
On Sat, Jun 6, 2020 at 11:47 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> I’m guessing this is an old message that just got admitted once Luke flushed the filters.
>
> Yehowshua
> _______________________________________________
> 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] Introduction and Questions
From: Yehowshua @ 2020-06-06 22:47 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAEoCstTQPSUf0HXdj5pmk+JYw3i4aaWhKEb2CS_Q1PqGdFfz3g@mail.gmail.com>
I’m guessing this is an old message that just got admitted once Luke flushed the filters.
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] Contributing to the Libre-Soc Project
From: Sanjay Menon @ 2020-06-06 22:29 UTC (permalink / raw)
To: libre-riscv-dev
Hi,
I am a budding VLSI enthusiast and open-source developer. I would love to
work with the team in your goal to achieve a completely open source project.
I believe that as a beginner in this area, I would be able to learn more
from you guys as I contribute to this wonderful project.
I thank Yehowshua Immanuel for introducing me to this project. Can't wait
to start already. Hoping to hear from you soon.
To know more about me do checkout my LinkedIn
<http://www.linkedin.com/in/sanjay-menon-91791815a> profile.
Thanks and regards,
Sanjay A Menon
_______________________________________________
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] Introduction and Questions
From: Jeremy Singher @ 2020-05-15 6:50 UTC (permalink / raw)
To: libre-riscv-dev
Hi all,
My name is Jeremy Singher. I'm a graduate student studying computer
architecture, interested in open-source hardware and high performance
microarchitectures. I am looking for an open-source hardware project I can
contribute to through the course of my graduate studies, and I have some
questions about the Libre-SOC project.
1. It seems like you guys are building various components of an
out-of-order microarchitecture, such as the scoreboard, and load-store
ordering units. Do you have a complete microarchitecture diagram of the
core (or a text description)? I could find bits and pieces on specific
components, but I'm interested in details like pipeline width, depth,
branch-to-branch latency, load-use delay, etc.
2. Is the SoC at a state at which I can evaluate performance on simple
benchmarks in simulation? Other similar open-source hardware projects have
make targets to launch verilator simulations, but I could not find an
equivalent in your repos (although I probably am just bad at looking).
3. What is your target performance in terms of an established benchmark
like Coremark, Dhrystone, Embench, or SPEC? I'm trying to compare the
merits and progress of various hardware projects out-there.
4. What is the right way to get started contributing? My experience is with
Verilog, and I've looked at other languages too, including BSV and Chisel.
I'm primarily interested in developing microarchitecture for
performance-critical components, like branch predictors, prefetchers,
instruction schedulers, and load-store units. Ideally, I could contribute
my work as part of graduate studies to this project.
Sorry for the barrage of questions.
Best,
-Jeremy
_______________________________________________
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 336] ALU CompUnit needs to recognise that RA (src1) can be zero
From: bugzilla-daemon @ 2020-06-06 22:38 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-336-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=336
--- Comment #52 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cesar Strauss from comment #51)
> (In reply to Luke Kenneth Casson Leighton from comment #50)
> > if you feel it does not take a long time to "fix" alu_hier.py ALU classes
> > please do go ahead.
>
> One more thing. These test ALUs are non-pipelined, right? I mean, they take
> a finite number of cycles to sequence through their stages, but are not able
> to accept a new operation, each cycle, meanwhile, right?
correct. this is to simulate FSMs (such as a DIV operation) and also to
provide a way to check that the MultiCompUnits work properly when there is a
delay.
it is a SEVERE violation of the entire MultiCompUnit API for a MCU to expect to
process (generate) more than one result at a time.
this because that implies that it is "abandoning" a result, in direct violation
of its role and responsibility to monitor the result through to completion.
the way to use pipelines: for an N Stage Pipeline, have a minimum of N
MultiCompUnits with a fan-in and fan-out. this is what the class
ReservationStations is for.
the whole purpose of writing this parallel test is to be able to work towards
the scenario of doing exactly that: have Nx MultiCompUnits throw 100-200
results at a pipeline (a "proper" N-stage pipeline) and check that the results
are consistent.
however that is for later.
> In this case, I think setting ready_o combinatorially, based on valid_i
> being high, and the sequence counter being zero, is enough. This will even
> keep ready_o from activating if valid_i is high and the ALU is still busy.
> Will check if it works.
go for 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 336] ALU CompUnit needs to recognise that RA (src1) can be zero
From: bugzilla-daemon @ 2020-06-06 21:20 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-336-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=336
--- Comment #51 from Cesar Strauss <cestrauss@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #50)
> if you feel it does not take a long time to "fix" alu_hier.py ALU classes
> please do go ahead.
One more thing. These test ALUs are non-pipelined, right? I mean, they take a
finite number of cycles to sequence through their stages, but are not able to
accept a new operation, each cycle, meanwhile, right?
In this case, I think setting ready_o combinatorially, based on valid_i being
high, and the sequence counter being zero, is enough. This will even keep
ready_o from activating if valid_i is high and the ALU is still busy. Will
check if it works.
--
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 336] ALU CompUnit needs to recognise that RA (src1) can be zero
From: bugzilla-daemon @ 2020-06-06 20:53 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-336-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=336
--- Comment #50 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cesar Strauss from comment #49)
> I'm advancing on the ALU CompUnit parallel unit test. Having gone past the
> rd rel/go interface, I've moved on to the ALU input interface.
>
> The ALU input interface uses a valid/ready protocol. I assume that this,
> like rel/go, is similar to the wishbone interface.
standard wishbone / AXI4 yes. the difference being that rel/go will NEVER be
back to back (multiple transactions one after the other) however ready/valid
can be.
however in the MultiCompUnits it is never used for that, because MCU is single
transaction only.
> As such:
>
> 1) The port is idle when valid_o and ready_i are both zero.
> 2) If valid_o is high but ready_i is low, we have a wait state.
> 3) When both are high, we have a data transfer, and the transaction ends.
or, takes place on that clock cycle, abd ends "as far as the next clock cycle
is concerned".
> 4) It is illegal to keep ready_i high when valid_o is low.
> This is supposed to cover a single transaction, but in my undestanding I see
> 5 acknolowdged back-to-back transactions followed by a illegal state.
this does not surprise me. the alu_hier.py ALUs were written "in a hurry" and
are there purely for test purposes only.
> Can I go ahead and fix all these cases, to be more like wishbone? Or, is my
> assumption of wishbone likeness wrong?
yes please do...
or...
last week i considered throwing them out and using nmutil.singlepipe ALUs
instead.
if you feel it does not take a long time to "fix" alu_hier.py ALU classes
please do go ahead.
otherwise if it will take a long time it would be better to drop them and
replace them with ALUs based on e.g. TestBufPipe (see nmutil unit tests)
again: they are only there for test purposes, however as tests it is indeed
good for them to properly conform to the required API
--
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 336] ALU CompUnit needs to recognise that RA (src1) can be zero
From: bugzilla-daemon @ 2020-06-06 20:33 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-336-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=336
--- Comment #49 from Cesar Strauss <cestrauss@gmail.com> ---
I'm advancing on the ALU CompUnit parallel unit test. Having gone past the rd
rel/go interface, I've moved on to the ALU input interface.
The ALU input interface uses a valid/ready protocol. I assume that this, like
rel/go, is similar to the wishbone interface. As such:
1) The port is idle when valid_o and ready_i are both zero.
2) If valid_o is high but ready_i is low, we have a wait state.
3) When both are high, we have a data transfer, and the transaction ends.
4) It is illegal to keep ready_i high when valid_o is low.
As a diagram:
clk 1 2 3 4 5 6
data_i . D D D D .
valid_i . 1 1 1 1 .
ready_o . . . . 1 .
latched . . . . D .
Back to back transactions are also permitted:
clk 1 2 3 4 5 6
data_i . A A B C .
valid_i . 1 1 1 1 .
ready_o . . 1 1 1 .
latched . . A B C .
Well, while tracing the ALU input handshake, in the parallel unit test, in
src/soc/experiment/test/test_compalu_multi.py, I found this:
clk 1 2 3 4 5 6
CompUnit: valid_i . . 1 1 . .
ALU: ready_o . . . 1 1 .
^
trouble
On cycle 5, ready_o is still high while valid_i is low. This can generate
trouble if ready_o is wired-or with other modules.
Worse yet, on the src/soc/experiment/alu_hier.py unit test:
valid_i . . 1 1 1 1 1 1 . .
ready_o . . . 1 1 1 1 1 1 .
This is supposed to cover a single transaction, but in my undestanding I see 5
acknolowdged back-to-back transactions followed by a illegal state.
Can I go ahead and fix all these cases, to be more like wishbone? Or, is my
assumption of wishbone likeness wrong?
--
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 06jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-06 13:09 UTC (permalink / raw)
To: Libre-RISCV General Development
yesterday:
* bit more on core.py, disabled CR check for now. michael to review over w/e
* looked over DualPortSplitter, made some notes
* noticed that all pipe_data.py can be constructed from regspecs. removed
hardcoding.
* lots of codemorph and whitespace cleanup
* put a preliminary version of mtmsr into the mdwn for Cole to check
today:
* decided to add a LDST compunit test so that LDST can be added to the
simple core.py
* add XER regfile check into test_core.py
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 329] coriolis2 experiment layout for Dependency Matrices
From: bugzilla-daemon @ 2020-06-06 12:25 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-329-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=329
--- Comment #15 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jean-Paul.Chaput from comment #14)
> (In reply to Luke Kenneth Casson Leighton from comment #13)
> > $(FLATLO) does not appear to be defined. looking for it now.
>
> Sorry, I just did a commit into alliance-check-toolkit to
> correct it.
ah thanks :)
--
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 329] coriolis2 experiment layout for Dependency Matrices
From: bugzilla-daemon @ 2020-06-06 12:23 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-329-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=329
--- Comment #14 from Jean-Paul.Chaput@lip6.fr ---
(In reply to Luke Kenneth Casson Leighton from comment #13)
> $(FLATLO) does not appear to be defined. looking for it now.
Sorry, I just did a commit into alliance-check-toolkit to
correct 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 329] coriolis2 experiment layout for Dependency Matrices
From: bugzilla-daemon @ 2020-06-06 11:23 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-329-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=329
--- Comment #13 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
$(FLATLO) does not appear to be defined. looking for it now.
--
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 329] coriolis2 experiment layout for Dependency Matrices
From: bugzilla-daemon @ 2020-06-06 11:20 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-329-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=329
--- Comment #12 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
hiya jean-paul, thank you so much for this detailed and dedicated work.
i will come back to an answer things when i can see the layout.
i am walking through replicating the results, and encounter this after
"make vstf" - any clues?
r test_fu_fu_matrix test_fu_fu_matrix_flat
make: r: Command not found
--
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 55] IOpad Cell Library needed with industry-standard GPIO and DDR capability
From: bugzilla-daemon @ 2020-06-06 11:03 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-55-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=55
--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Staf Verhaegen from comment #4)
> I want to add that also DDR signaling is left to be implemented in the logic
> circuit on top of the level-shifted core output. It typically is done by
> using both a rising edge and a falling edge triggered flip-flop on this
> output.
this is fantastic, staf. look forward to hearing how the test goes.
--
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 329] coriolis2 experiment layout for Dependency Matrices
From: bugzilla-daemon @ 2020-06-06 10:41 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-329-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=329
--- Comment #11 from Jean-Paul.Chaput@lip6.fr ---
(In reply to Luke Kenneth Casson Leighton from comment #10)
> (In reply to Jean-Paul.Chaput from comment #9)
> > (In reply to Luke Kenneth Casson Leighton from comment #8)
Hello Luke,
I posted in the soclayout & Coriolis repository a first trial at getting
back matrix like structures. It is *only* tailored for the FU-FU matrix
30x30 (hardcoded in the Coriolis plugin).
I added a Makefile to allow you to run it conveniently.
* Generate & flatten the netlist in vst:
> make vstf
* You call the plugin in graphical mode in:
> make viewf
Then, in the menus:
Misc -> Beta -> Matrix Placer
It is slow (~5 minutes) and there is no algorithmic reasons to,
almost everything is linear or log(n).
The important conclusion I draw with this preliminary work, is
that the automatic placer is doing better that the matrix placer.
You can see the results in RESULTS.txt.
Why is that so?
* The automatic placer is good, in graphic mode you can see him finding
back the matrix structure.
* The matrix placer lose space as each block of the matrix as a ragged
right edge where you systematically lose space. Of course it can be
improved, but in the end you may just reach the 5% of marging of
the automated placer.
* The conclusion about total wire length is less clear, seems close to
each other. But with uneven density for the matrix placer, so a
little bit more difficult to route.
* So we may spend a lot of time for almost no significant improvement.
So, it seems to me that Staf wins... The approach we should take is feed
it directly amost as a whole to the P&R (except for RAM). If the tools
cannot cope, we may broke it in 50Kgates blocks.
* The matrix placement may still win, but with a different approach.
Build a manual generator from the groud up. Do not use synthesis
then try to guess back the placement. But it is a lot of work
with all the various cases you want to manage.
Best regards,
--
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 55] IOpad Cell Library needed with industry-standard GPIO and DDR capability
From: bugzilla-daemon @ 2020-06-06 10:35 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-55-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=55
--- Comment #4 from Staf Verhaegen <staf@fibraservi.eu> ---
I want to add that also DDR signaling is left to be implemented in the logic
circuit on top of the level-shifted core output. It typically is done by using
both a rising edge and a falling edge triggered flip-flop on this output.
--
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 55] IOpad Cell Library needed with industry-standard GPIO and DDR capability
From: bugzilla-daemon @ 2020-06-06 10:26 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-55-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=55
--- Comment #3 from Staf Verhaegen <staf@fibraservi.eu> ---
The current IO cell design can be used to get most of the requirements. Some
clarification:
* There is a level shifted output from the external 3.3V pad voltage to an 1.8V
cell output to the core; this signal is asynchronous. It is meant that digital
logic is added on this output to implement things like meta-stability
prevention, debouncing and IRQ generation.
* The block has separate inputs for enabling each of the sink and the source
drivers. So if all drivers are disabled the output is high impedance and can
driven from an external driver; e.g. in this state the IO cell functions as an
input IO cell.
* There is a distinction between Schmidtt triggering and signal debouncing.
Schmidtt triggering means that the switching threshold is different for a
rising edge than for a falling edge. This is to avoid oscillation in the
level-shifted core output for slowly moving noisy input signals. With signal
debouncing typically stands for the filtering out of mutiple full swing signal
swings like one get from push buttons etc.
Current implementation of the level-shifting does not include Hysteresis but it
should be easy to add for the prototype. As said in first point thoough, signal
debouncing is left to the digital logic connected to the level-shifted output
of the IO cell.
--
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 325] create POWER9 TRAP pipeline
From: bugzilla-daemon @ 2020-06-06 2:23 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-325-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=325
--- Comment #62 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
> (In reply to Luke Kenneth Casson Leighton from comment #59)
> > (In reply to Cole Poirier from comment #57)
> > > This is done. Should I start trying to figure out how to write these unit
> > > tests using fu/cr/test/test_pipe_caller as a guide?
> >
> > yes sure. although bear in mind that only the instructions which are
> > supported
> > in the emulator will work.
>
> Oh interesting, is this our fork of gem5?
no
> Or is this the one that is
> generated from parsing the csv files?
yes. hence the need for the pseudocode. until that exists there *is* no mfmsr
(etc) to test against!
in this case even the TRAP function has to be written.
this would (in python) move the SPRs about, set NIA to 0x700 blah blah.
> > > Or if this will be
> > > outside of my current capacity, should I move on to bug #348?
> >
> > generally speaking if there are several tasks which you can do, just
> > do another if you're blocked: don't wait to ask, just do it.
>
> Don't worry, like 'waiting days or hours between commits' this is a bad
> habit you helped me break a few weeks ago.
:)
> > i've done a git push on the libre-soc repo you should be able to retry.
>
> Hmm yes, looking at the pseudo-code you've written there is no way I would
> have figured out all of the necessary modifications to the spec pseudo code
> needed to get the parser to validate it. Thanks for doing this for me, with
> this knowledge I think I'll be able to do it solo next time.
cool.
the syntax is python-indented (that was a pig to implement), and borrowed
python concepts such as brackets. i replaced operators such as = with <- and
so on.
subscripted ranges were obviously not possible to do in ASCII so i did straight
brackets python slices but kept the POWER numbering.
so the translator pushes an extra +1 out on the "end" of the slice.
you saw that when doing bperm.
--
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 05jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-06 2:13 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <BD01F5CC-5368-4830-84CD-FD4D9297BDF5@getmailspring.com>
On Saturday, June 6, 2020, Cole Poirier <colepoirier@gmail.com> wrote:
>
> * Put together a first draft of iot-rtos business-deck for review and
> comments by Yehowshua, which I will then modify and polish for a second
> review Sunday
nice.
> Given that the above is not related to Libre-SOC general development, is
> the appropriate place to communicate about this a new dedicated mailing
> list? I'm unsure of how to proceed here Luke, being mindful of our
> obligation to be fully transparent (but to also not to bother technical
> people like Jean-Paul), and also of the fact that I do not fully
> understand the relationship between Libre-SOC and Systemes Libres, and
> any implications this may have. Help please :)
yes we need more mailing lists. need to move to libresoc ones too. alain
set them up. just haven't moved over.
raise bugreport. discuss there.
--
---
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] GPU Drivers ROCM
From: Luke Kenneth Casson Leighton @ 2020-06-06 2:10 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <776743AB-327C-43E6-B24A-2BE1FC2AE3E2@gatech.edu>
On Saturday, June 6, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:
> It recently occurred to me that the entire ROCM stack is open.
> ROCM also has, OpenGL, Vulkan, OpenCL, and CUDA -> HIP
> frontends.
https://github.com/RadeonOpenCompute/ROCm
> At the very bottom of ROCM sits llvm which emits AMD GPU opcodes.
according to the diagram, NVIDIA CUDA GPU opcodes as well
>
> It **should be possible to modify this emitter for our GPU. Then we’d
> virtually
> have to do little to no work.
indeed.
another possibility is to actively support AMDGPU opcodes.
this is the aporoach taken by MIAOW (a subset of).
> I’m actively investigating if this is possible and am trying to start a
> conversation
> with some ROCM engineers.
remember to emphasise to them that we are doing a hybrid CPUGPU. that the
usual route of a full IPC / RPC mechanism communicating to a foreign remote
architecture is gone, and any complex IPC/RPC inter-kernel bridge code is
entirely gone, replaced with *direct* executed assembly code.
otherwise they will think that the conversation involves us being a
Vivante, or a MALI, and consequently they will think that you are talking
about 10, 20 or greater man-years of work, whereas what you are actually
talking about is of the order of around 1 maybe 2.
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] GPU Drivers ROCM
From: Yehowshua @ 2020-06-06 1:29 UTC (permalink / raw)
To: Libre-RISCV General Development
It recently occurred to me that the entire ROCM stack is open.
ROCM also has, OpenGL, Vulkan, OpenCL, and CUDA -> HIP
frontends.
At the very bottom of ROCM sits llvm which emits AMD GPU opcodes.
It **should be possible to modify this emitter for our GPU. Then we’d virtually
have to do little to no work.
I’m actively investigating if this is possible and am trying to start a conversation
with some ROCM engineers.
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 05jun2020
From: Cole Poirier @ 2020-06-06 0:03 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDzM0+eDz+FbWdLH59YN37WHZDM+7n+=Dre1dWYxvbaz4Q@mail.gmail.com>
Today:
* Worked with Luke on TRAP pipeline.
* Had a call with Yehowshua about Systemes Libres. I'm going to help him
with the 'business-deck' for the upcoming Wednesday meeting with Amazon
Alexa IOT, specifically focussing on pitching Libre-SOC in the rtos,
edge compute, and consumer IOT market segments
* We discussed that going forward he and I will collaborate on the
business-deck pitches, and I will do some work focussed on the design
and marketing aspects of the website. In addition to this I will be
helping to reach out to and follow up with potential new developers in
an effort to get more people working on Libre-SOC.
Tomorrow:
* Work on translating SPEC v3.0B pseudo-code to nmigen for the SPR
pipeline (bug #348 <https://bugs.libre-soc.org/show_bug.cgi?id=348>)
* Put together a first draft of iot-rtos business-deck for review and
comments by Yehowshua, which I will then modify and polish for a second
review Sunday
Given that the above is not related to Libre-SOC general development, is
the appropriate place to communicate about this a new dedicated mailing
list? I'm unsure of how to proceed here Luke, being mindful of our
obligation to be fully transparent (but to also not to bother technical
people like Jean-Paul), and also of the fact that I do not fully
understand the relationship between Libre-SOC and Systemes Libres, and
any implications this may have. Help please :)
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 325] create POWER9 TRAP pipeline
From: bugzilla-daemon @ 2020-06-05 23:46 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-325-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=325
--- Comment #61 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #58)
> yep, the pseudo-language is not documented, it's one of those things you
> have to look at other scripts and just work it out by inference.
>
> do a git pull on the libre-soc.org repo, i added the code to it there,
> you should find it works.
>
> one thing: you had a space in front of every line. that would not have
> worked:
> the parser was written very very quickly.
Ah that's just when I pasted it here (I'm 90% sure), not in the file, for some
reason buzilla likes to prepend a space when I'm pasting code here.
(In reply to Luke Kenneth Casson Leighton from comment #59)
> (In reply to Cole Poirier from comment #57)
> > This is done. Should I start trying to figure out how to write these unit
> > tests using fu/cr/test/test_pipe_caller as a guide?
>
> yes sure. although bear in mind that only the instructions which are
> supported
> in the emulator will work.
Oh interesting, is this our fork of gem5? Or is this the one that is generated
from parsing the csv files? I recall this being discussed on list but I can't
remember which one we are currently using.
> > Or if this will be
> > outside of my current capacity, should I move on to bug #348?
>
> generally speaking if there are several tasks which you can do, just
> do another if you're blocked: don't wait to ask, just do it.
Don't worry, like 'waiting days or hours between commits' this is a bad habit
you helped me break a few weeks ago. I ended up working on Systemes Libres
stuff with Yehowshua for Wednesday's meeting. I'll be leaving this bug for now,
to work on bug #348. After I finish the pseudo-code translation for that, I
plan come back to do the unit tests for this, unless, as often happens with the
project, plans change.
> > > 2) add the pseudocode to sprset.mdwn (yes sprset.mdwn is a bad name) from
> > > comment #47
> > >
> > > https://libre-soc.org/openpower/isa/sprset/
> >
> > Waiting on your help with this one, I figured I shouldn't waste more time on
> > it given that it's likely something that you're capable of identifying and
> > fixing in a matter of seconds because you understand the parser completely.
>
> actually i don't: it has been several months, and i wrote it very fast,
> to perform a minimal job!
>
> i've done a git push on the libre-soc repo you should be able to retry.
Hmm yes, looking at the pseudo-code you've written there is no way I would have
figured out all of the necessary modifications to the spec pseudo code needed
to get the parser to validate it. Thanks for doing this for me, with this
knowledge I think I'll be able to do it solo next time.
--
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 325] create POWER9 TRAP pipeline
From: bugzilla-daemon @ 2020-06-05 23:25 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-325-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=325
--- Comment #60 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
161 with m.If(a_i[MSR_PR]):
162 msr_o.data[MSR_EE].eq(1)
163 msr_o.data[MSR_IR].eq(1)
164 msr_o.data[MSR_DR].eq(1)
and at line 185 comb += is missing
--
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
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