* 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
* [libre-riscv-dev] [Bug 274] Investigate how BSV performs Formal Verification and what can be Applied to FPUs
From: bugzilla-daemon @ 2020-06-06 23:11 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-274-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=274
--- Comment #1 from Yehowshua <yimmanuel3@gatech.edu> ---
From what I can tell, formal is mostly applied in BSV to make sure that rules
are activated once their conditions are met.
--
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] Contributing to the Libre-Soc Project
From: Luke Kenneth Casson Leighton @ 2020-06-06 23:13 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: sanjayamenon.mec
In-Reply-To: <CAE_rhwZK4FeFHDh4SNiUozji1vR1L4Xm=+BVBRuxHMw49CsMhQ@mail.gmail.com>
(hi everyone please do cc sanjay as i've just manually approved this
message and he is not yet subscribed to the list, so would not see
replies unless explicitly cc'd. sanjay, do subscribe to the list via
the interface at
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev)
On Sat, Jun 6, 2020 at 11:47 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.
good to hear from you.
one key thing to appreciate: this is a libre project, not an "open
source" one. the distinction is not immediately apparent or
well-known to people, and it comes down to this: a Libre project says
"no" when it comes to unethical practices, whereas an "open" one makes
no such declaration. "open source" projects *might* have people
contributing to it with the very best of intentions, however none of
them will have *actively* declared not to cross an ethical line.
> 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.
well, one thing i love telling people the story is of how Cole Poirier
has gone from zero hardware knowledge to writing his own nmigen
modules. so there is room for everyone with all levels of experience.
> I thank Yehowshua Immanuel for introducing me to this project. Can't wait
> to start already. Hoping to hear from you soon.
so, congratulations on the first step - getting in touch (*tick*) :)
just go through the list on the "how can i help as a developer", in
your own time - https://libre-soc.org/
in particular you'll find the development workflow advice here:
https://libre-soc.org/HDL_workflow/
this is a combined page of best practices for collaboration, as well
as containing developer-style "getting started" instructions.
> To know more about me do checkout my LinkedIn
> <http://www.linkedin.com/in/sanjay-menon-91791815a> profile.
nice, i see you've done actual VLSI layout - we're using coriolis2,
this involves actually writing the layout *entirely as a python
program*:
https://bugs.libre-soc.org/buglist.cgi?quicksearch=coriolis2&list_id=826
if you'd like to do that, you're more than welcome (and can receive
donations from NLNet for doing so). there's plenty of other tasks as
well.
you have some cool projects on there, including implementing SHA256 in
hardware: did you do that at gate-level or in an HDL?
best,
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] FHDLTestCase
From: Luke Kenneth Casson Leighton @ 2020-06-06 23:15 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <8931BBAF-3BC2-43CD-BB7B-DD0AEAB17F2B@gatech.edu>
On Sun, Jun 7, 2020 at 12:03 AM Yehowshua <yimmanuel3@gatech.edu> wrote:
> Which reminds me, we need to separate FHDLTestCase class
> into the nmutils repo since it's no longer officially maintained.
(i've done that already. we also need to take a copy of the
nmigen._tools.py code. could you ask whitequark if she expects that
to also happen, that we create multiple copies of more and more code
from nmigen?)
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 274] Investigate how BSV performs Formal Verification and what can be Applied to FPUs
From: bugzilla-daemon @ 2020-06-06 23:19 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-274-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=274
--- Comment #2 from Yehowshua <yimmanuel3@gatech.edu> ---
The bsc source for generating a floating point adder is here:
https://github.com/B-Lang-org/bsc/blob/master/src/Libraries/Base3-Math/FloatingPoint.bsv#L1822
I'm not sure if it is formally verified.
--
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 274] Investigate how BSV performs Formal Verification and what can be Applied to FPUs
From: bugzilla-daemon @ 2020-06-06 23:22 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-274-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=274
--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Yehowshua from comment #1)
> From what I can tell, formal is mostly applied in BSV to make sure that
> rules are activated once their conditions are met.
it's... complicated. the "rules" are a bit like pre-conditions from
advanced (very obscure) software engineering languages.
in combination with extremely strict (strong) typing (which i can tell
you from experience MASSIVELY interferes with and impedes development
progress), the end result is code that is absolutely 100% guaranteed
to be synthesiseable.
it's actually stronger than that: because they are using Haskell, they
have an internal Formal Correctness Proof that a program that compiles
is 100% *mathematically* guaranteed to be gate-level synthesiseable.
verilog as you know is completely incapable of making such guarantees.
this tends to fit with what you've heard about it being "able to
generate formally verified adders".
*actual* formal verification however i believe is done slightly differently,
and i've not investigated it, other than i saw a talk by Nihil for a
RVF presentation, and the code that he wrote looked extremely obvious and
easy to understand and read. the "magic" i expect was happening somewhere
behind the scenes.
--
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] FHDLTestCase
From: Yehowshua @ 2020-06-06 23:22 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxD72iib+ieBdNr6HVgHnkQDbq=5jogFj+VMR-Q6fSSCg@mail.gmail.com>
>
>> Which reminds me, we need to separate FHDLTestCase class
>> into the nmutils repo since it's no longer officially maintained.
>
> (i've done that already. we also need to take a copy of the
> nmigen._tools.py code. could you ask whitequark if she expects that
> to also happen, that we create multiple copies of more and more code
> from nmigen?)
>
Just now seeing this. Glad you did that!
I’ll ask.
_______________________________________________
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] FHDLTestCase
From: Yehowshua @ 2020-06-06 23:27 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <34CE8AF9-38A7-49C1-8F19-F8DC89EFE350@gatech.edu>
But from what she told me, anything with `_` prefix
has not guarantees of maintaining a stable interface.
So if we’ve been importing from `_`, that’s on us.
Other than that, we should be fine.
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] FHDLTestCase
From: Luke Kenneth Casson Leighton @ 2020-06-06 23:34 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <34CE8AF9-38A7-49C1-8F19-F8DC89EFE350@gatech.edu>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Sun, Jun 7, 2020 at 12:22 AM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> >
> >> Which reminds me, we need to separate FHDLTestCase class
> >> into the nmutils repo since it's no longer officially maintained.
> >
> > (i've done that already. we also need to take a copy of the
> > nmigen._tools.py code. could you ask whitequark if she expects that
> > to also happen, that we create multiple copies of more and more code
> > from nmigen?)
> >
>
> Just now seeing this. Glad you did that!
from nmigen._toolchain import require_tool
https://git.libre-soc.org/?p=nmutil.git;a=blob;f=src/nmutil/formaltest.py;hb=HEAD
> I’ll ask.
basically, without coming out and actually saying "this is completely
ridiculous, it leads down a rabbithole of copying more and more of
nmigen into a separate repository, which everyone else will likewise
have to do", we need to slowly and diplomatically educate her in the
python collaborative practices that she's missing.
nmigen is extremely unusual in that it is a "root" project (zero
external dependencies). it's self-contained, is whitequark's first
experience with python, and consequently she has *zero* experience of
python collaborative development practices that have taken 20 years to
establish.
given that nmigen may well be the very first time that some HDL
engineers ever *use* python extensively (Staf, for example i believe
may fall into this category), there is a huge responsibility that
falls on whitequark's shoulders to learn and then make sure to use
best collaborative python practices. and it is a huge responsibility.
unfortunately, my efforts to communicate with her about this did not
go well. when i spoke with her about the extremely damaging practice
of using wildcard imports, rather than go "ah: i understand how this
is extremely detrimental to collaborative development, i will give it
some thought", her response was, "the python programming language
should not be broken. it is not my responsibility: it is the
responsibility of the python developers. they should never have added
the feature".
to her credit she *is* responding on some things. usually it takes
more than one person to communicate with her about a given issue.
over time, she'll get it, i am sure, as she is extremely intelligent.
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 364] New: Python YosysCXX Interface
From: bugzilla-daemon @ 2020-06-06 23:41 UTC (permalink / raw)
To: libre-riscv-dev
https://bugs.libre-soc.org/show_bug.cgi?id=364
Bug ID: 364
Summary: Python YosysCXX Interface
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: yimmanuel3@gatech.edu
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
Whitequark is currently working on this.
--
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 364] Python YosysCXX Interface
From: bugzilla-daemon @ 2020-06-06 23:41 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-364-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=364
Yehowshua <yimmanuel3@gatech.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
total budget (EUR)|0 |4000
for completion of| |
task and all| |
subtasks| |
NLnet milestone|--- |NLNet.2019.10.Wishbone
Assignee|lkcl@lkcl.net |whitequark@whitequark.org
--
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] FHDLTestCase
From: Yehowshua @ 2020-06-06 23:45 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwo92zyApEmnqRHrVxFAySFSjD1=k7Xp6e0myjH6M55jg@mail.gmail.com>
nMigen is in active development.
At somepoint, we may have to make nMigen a
submodule frozen at a particular commit anyways.
We do have tests, so we’ll know when things start breaking.
We’ll take it one thing at a time.
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] FHDLTestCase
From: Luke Kenneth Casson Leighton @ 2020-06-06 23:45 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <7D3C94B7-A88A-4984-B71C-9ADFB0903C18@gatech.edu>
On Sun, Jun 7, 2020 at 12:28 AM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> But from what she told me, anything with `_` prefix
> has not guarantees of maintaining a stable interface.
correct. and therefore the implications are: we must take a copy of
that code in order for it to be "maintained as a stable interface".
> So if we’ve been importing from `_`, that’s on us.
uh-huh. and we just had to quotes take a copy of FHDLTestCase quotes.
and, because FHDLTestCase - which she wrote - uses nmigen._toolchain,
we must now quotes take a copy of _toolchain.py quotes.
... you see where that leads?
absolutely every single python nmigen developer must quotes take
copies of code quotes in order to guarantee that they have a stable
API to work with.
now, it *might* be the case that somebody notices that we have quotes
taken a copy of FHDLTestCase quotes and also quotes taken a copy of
_toolchain.py quotes.
they *might* use nmutil because of that, and thus avoid code-duplication.
however the much more likely scenario is that they will likewise take
copies of that code, maintain completely separate copies (effectively
hard forks).
the bottom line is that this, slowly, will demonstrate to whitequark
what the *actual* role and responsibility of being an open
collaborative software development maintainer is. it's *not* to say
"this is not my responsibility, *i* declare - end of discussion - that
this is outside of scope of *my* project: if you try to use what *I
DECLARE* is private, that is YOUR problem", it's to be the gateway of
a *two-way* conversation.
i fully get that she is concerned about changing the API, and wants
the freedom and flexibility to change the internals. python
unfortunately doesn't work that way.
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] FHDLTestCase
From: Luke Kenneth Casson Leighton @ 2020-06-06 23:49 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <E19BAAA1-A6B0-485F-BD25-26CB8A8E5ACB@gatech.edu>
On Sun, Jun 7, 2020 at 12:45 AM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> nMigen is in active development.
yehyeh.
> At somepoint, we may have to make nMigen a
> submodule frozen at a particular commit anyways.
when the ASIC layout is being done, this will be a hard requirement.
Jean-Paul explained that it is Industry Standard Practice to have full
reproducible builds, fully automated in all respects. not even the
username / login changes (nobody has separate usernames in the
repro-build scripts: even the username is exactly the same, added as
part of the OS clone/install script).
> We do have tests, so we’ll know when things start breaking.
yehyeh.
> We’ll take it one thing at a time.
:)
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 364] CXXRTL Python Interface
From: bugzilla-daemon @ 2020-06-06 23:55 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-364-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=364
Yehowshua <yimmanuel3@gatech.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Python YosysCXX Interface |CXXRTL Python Interface
--
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 362] improvements to nmigen and yosys
From: bugzilla-daemon @ 2020-06-06 23:55 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-362-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=362
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
budget (EUR) for|0 |6000
completion of task| |
(excludes budget| |
allocated to| |
subtasks)| |
--
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 365] New: ROCM/Libre-SOC GPU Opcode interoperability
From: bugzilla-daemon @ 2020-06-06 23:57 UTC (permalink / raw)
To: libre-riscv-dev
https://bugs.libre-soc.org/show_bug.cgi?id=365
Bug ID: 365
Summary: ROCM/Libre-SOC GPU Opcode interoperability
Product: Libre-SOC's first SoC
Version: unspecified
Hardware: PC
OS: Mac OS
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: Source Code
Assignee: lkcl@lkcl.net
Reporter: yimmanuel3@gatech.edu
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
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.
--
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 365] ROCM/Libre-SOC GPU Opcode interoperability
From: bugzilla-daemon @ 2020-06-06 23:58 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-365-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=365
--- Comment #1 from Yehowshua <yimmanuel3@gatech.edu> ---
http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-June/007721.html
--
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 364] CXXRTL Python Interface
From: bugzilla-daemon @ 2020-06-06 23:59 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-364-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=364
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lkcl@lkcl.net
parent task for| |362
budget allocation| |
--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Yehowshua from comment #0)
> Whitequark is currently working on this.
the last conversation we had was that Michiel was happy - provisionally - to
add this to the list of tasks for the NLet 2019-10-043 Grant (which has gone
through the "Approval" process). Michiel asked us to get back with a proposal,
and we did not hear back from you (whitequark) about that. i therefore wrote
something a couple of days ago, and added it to bug #175
please do note: *we haven't had this approved by NLNet yet*. i sent Michiel a
message a couple days ago and will be following up with him about it by phone
some time early next week.
--
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 364] CXXRTL Python Interface
From: bugzilla-daemon @ 2020-06-07 0:01 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-364-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=364
--- Comment #2 from Yehowshua <yimmanuel3@gatech.edu> ---
Is there a proposal template?
Something like this?
https://libre-soc.org/nlnet_2018/
--
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] Successful subscription
From: Sanjay Menon @ 2020-06-07 0:01 UTC (permalink / raw)
To: libre-riscv-dev
Hi,
I did finally manage to get myself subscribed to the mailing list.
Thanks to a little help from Yehowshua.
I would be checking out the nMigen tool.
As for my SHA256 IP, I currently have done 2 implementations of the same.
1. Using the Vivado HLS environment
2. Using Verilog
Currently working on an implementation of a SHA256 cracker using HLS.
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] [Bug 364] CXXRTL Python Interface
From: bugzilla-daemon @ 2020-06-07 0:25 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-364-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=364
--- Comment #3 from Yehowshua <yimmanuel3@gatech.edu> ---
> please do note: *we haven't had this approved by NLNet yet*. i sent Michiel
> a message a couple days ago and will be following up with him about it by
> phone some time early next week.
I see the paragraph added to the end of bug #175.
I'm guessing that's all that's needed.
Nothing as elaborate as the early NLNet proposals.
--
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] Successful subscription
From: Luke Kenneth Casson Leighton @ 2020-06-07 0:27 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAE_rhwY8Z3L_iO0Qu0qH6Uw4WnJH+whAjgLrBbY6CYMBmyTrqg@mail.gmail.com>
On Sun, Jun 7, 2020 at 1:01 AM Sanjay Menon <sanjayamenon.mec@gmail.com> wrote:
>
> Hi,
>
> I did finally manage to get myself subscribed to the mailing list.
hooray! :) bear in mind that this is considered a high-traffic list.
you may wish to look at setting up filters (gmail can do that) - in
particular i recommend creating a special folder for anything that
comes from the bugzilla libre-soc address.
> Thanks to a little help from Yehowshua.
>
> I would be checking out the nMigen tool.
robert baruch's tutorial is extremely good to get started, yehowshua
sent the link.
the main thing that you need to get your head round for nmigen is that
unlike MyHDL, you *use* python to construct an in-memory Abstract
Syntax Tree. this AST is then passed to a nmigen function, which
simply walks that AST and outputs yosys ILANG files (or verilog files,
if you ask it to).
MyHDL is a *language translator* (not a compiler) that actually takes
the actual python code and transliterates into VHDL. thus, in MyHDL,
you absolutely cannot use python exceptions, or many OO techniques,
because those concepts simply do not exist at the Gate Level, in
hardware.
in nmigen we are entirely at liberty to use the *full* capabilities of
python OO programming, and we do so extensively.
the closest that Verilog has to even the most basic capability that we
use all the time in nmigen: parameters in modules. we also pass
parameters to the class constructor (or a python function) which
changes the size of the array, or the width of the signals, and so on.
> As for my SHA256 IP, I currently have done 2 implementations of the same.
> 1. Using the Vivado HLS environment
> 2. Using Verilog
oh good. so you're used to working "indirectly", so to speak. that's
very good. that experience - writing in C i presume? - then comparing
the same implementation in Verilog - this will stand you in good stead
when working with nmigen.
when you follow robert baruch's tutorial, i recommend you also explore
generating verilog output from the examples, and have a look at what
is produced. it's... sort-of readable, and you will quickly get used
to seeing how there is a direct equivalence between the nmigen and
verilog.
> Currently working on an implementation of a SHA256 cracker using HLS.
nice :)
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 364] CXXRTL Python Interface
From: bugzilla-daemon @ 2020-06-07 0:28 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-364-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=364
--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Yehowshua from comment #3)
> > please do note: *we haven't had this approved by NLNet yet*. i sent Michiel
> > a message a couple days ago and will be following up with him about it by
> > phone some time early next week.
>
> I see the paragraph added to the end of bug #175.
> I'm guessing that's all that's needed.
yes. that's all that's needed.
> Nothing as elaborate as the early NLNet proposals.
correct. it's a discretionary decision that NLNet can take because they've
already gone through the (3-4 month) Approval Process.
--
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 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-06-07 0:29 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-184-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=184
Cole Poirier <colepoirier@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |colepoirier@gmail.com
--- Comment #17 from Cole Poirier <colepoirier@gmail.com> ---
Since we have completed the domain move, and we now have pitch meetings with
potential investors coming up, I think it is essential that we set up the
Libre-SOC-Org mailing list.
In addition to this, I'd like to suggest that we have a short weekly meeting
(~30 min) to discuss organizational matters, which should be recorded and made
available somehow. I found the OPF virtual coffee call to be very good for
adding some more connection to our highly distributed team. I think the purpose
of these meeting should be to discuss and layout proposals, for further
discussion on, and subject to unanimous approval by the Libre-SOC-Org mailing
list.
I'm writing this here because it's directly related to mailing lists. If you
find my idea of the video organizational chats to be worthy of further
discussion, then I think this will merit the creation of a new bug report.
I think it's also a good idea to add a new category of bug report to the thee
existing "Libre-SOC Website", "Libre-SOC First SOC", and "TODO IIT Madras 180nm
Foundry", perhaps "Systemes Libres Organization", such that technical bugs are
not mixed with non-technical bugs.
--
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