Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* Re: [libre-riscv-dev] LD/ST now a bit better. extra NLNet budgets
From: Luke Kenneth Casson Leighton @ 2020-06-11 19:41 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <ABC5750B-6FEB-429B-A3DE-5DCC95C0574E@gatech.edu>

On Thursday, June 11, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

> >
> > a full half of that first EUR 50,000 budget was allocated to
> > Kazan.
>
> On the note of Kazan, what is currently being done there?


nothing for the moment as we need all hands that have some nmigen
experience on the POWER9 core.


> I contacted Anton from Embox, he worked on the Etna-viv drivers
> and he recently joined the mailing list.
>
> Anton, don’t be shy to say hi :)


hi anton, great to know you're around, we have a budget for 3D driver work
if you're interested?

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] Kazan status
From: Jacob Lifshay @ 2020-06-11 20:56 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzKH_3+=AMte97EeSy_mznCCWwSovb5s-SxDvw-uQv6dg@mail.gmail.com>

On Thu, Jun 11, 2020, 12:42 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Thursday, June 11, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> > >
> > > a full half of that first EUR 50,000 budget was allocated to
> > > Kazan.
> >
> > On the note of Kazan, what is currently being done there?
>
>
> nothing for the moment as we need all hands that have some nmigen
> experience on the POWER9 core.
>

I'm taking a break on Kazan as stated above, Kazan's current status is that
the SPIR-V to shader-compiler-ir translator and creating shader-compiler-ir
is somewhere around half complete, I've been writing both of those together
to allow rapid modifications to shader-compiler-ir to add support for
SPIR-V features as I encounter them in the process of writing the
translator. At that point, writing the shader-compiler-ir language
reference docs will be the next step, since many of the invariants that the
code follows is not really documented yet. Once shader-compiler-ir is
stable and documented, it will be much more practical to have multiple
people work on different parts of the compiler at the same time, since the
basic interface will not change as much. After that, writing a reference
interpreter will allow us to run some actual shaders, writing the SIMT to
vector translator (the vectorization pass) will be enough to get to where
we should be able to run shaders with the expected execution model and
allow us to have all the parts for a working interpreted shader stack.
Next, writing the shader-compiler-ir to LLVM IR translator and JIT
compiler, creating a trait for a generic shader compiler backend (the part
that translates the final shader-compiler-ir to machine code and allows
executing the JIT compiled code or an interpreter) will allow us to have a
MVP working shader compiler, as well as settling the interface between the
rest of the Vulkan driver and the shader compiler crates.

>
>
> > I contacted Anton from Embox, he worked on the Etna-viv drivers
> > and he recently joined the mailing list.
> >
> > Anton, don’t be shy to say hi :)
>
>
> hi anton, great to know you're around, we have a budget for 3D driver work
> if you're interested?
>

Hi anton, glad to have additional people around who know a lot about 3D
drivers.

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

^ permalink raw reply

* Re: [libre-riscv-dev] daily kan-ban update 11jun2020
From: Jacob Lifshay @ 2020-06-11 20:58 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDx6Ztom8Phya75UioMGRcf1aVWnNhK=L1fp7rKKmQ-YqQ@mail.gmail.com>

today:
wrote up a short status report on Kazan
working on div and mul pipelines
attending OpenPower virtual coffee meeting

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

^ permalink raw reply

* Re: [libre-riscv-dev] daily kan-ban update 11jun2020
From: Cesar Strauss @ 2020-06-11 21:02 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDx6Ztom8Phya75UioMGRcf1aVWnNhK=L1fp7rKKmQ-YqQ@mail.gmail.com>

Ongoing:

* Work on the parallel test concept in
src/soc/experiment/test/test_compalu_multi.py.

Recently:

* Implement proper ready / valid signaling on the test ALU at
src/soc/experiment/alu_hier.py

Today:

* Looking into compldst_multi.py's unit tests to confirm that they are
properly functional
* (off-project): git bisecting systemd due to getting system freezes
after an upgrade. Fun.

Interesting tools and readings, to share:

* Pipelined Skid Buffer

http://fpgacpu.ca/fpga/Pipeline_Skid_Buffer.html

The circuit itself is useful, for meeting timing on long pipelines. But,
specially, I find it a nice example of the Finite State Machine (FSM)
technique, from requirements, concept and diagram, to design and
implementation. Doesn't cover unit tests and formal proofs, though.

* GTKWave package, from the PyVCD module

https://pyvcd.readthedocs.io/en/latest/vcd.gtkw.html

While used in a limited way by nMigen itself, for pre-filling traces in
a GTKWave window, it can do much more: comments, blank separators, trace
colors, scale, etc.

* Synchronous Resets? Asynchronous Resets? I am so confused! How will I
ever know which to use? by Clifford E. Cummings

http://www.sunburst-design.com/papers/CummingsSNUG2002SJ_Resets.pdf

* Clock Domain Crossing (CDC) Design & Verification Techniques Using
SystemVerilog, by Clifford E. Cummings

http://www.sunburst-design.com/papers/CummingsSNUG2008Boston_CDC.pdf

In particular, see section 5.8.2: Multi-bit CDC signal passing using
1-deep / 2-register FIFO synchronizer.

* Understanding Latency Hiding on GPUs, by Vasily Volkov

http://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-143.pdf

Nice introductory chapter on internal GPU architecture.

Regards,

Cesar

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

^ permalink raw reply

* [libre-riscv-dev] Handling POWERVec Instructions
From: Yehowshua @ 2020-06-11 21:21 UTC (permalink / raw)
  To: Libre-RISCV General Development

Just spitballing here…

But what we could do is trap and then scan the next 1024 instruction in software and JIT to SimpleV.

Maybe we should modify the Linux ELF loader so that in general, it scans binaries for any POWER instructions before placing them into memory, and if it sees any, it passes the binary to a POWERVec -> SimpleV jitter.

Jilting isn’t all that bad - after all - Android does it - and we only need it IF we have POWER instructions - which for most SBC use cases - is probably pretty rare.

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] Handling POWERVec Instructions
From: Luke Kenneth Casson Leighton @ 2020-06-11 21:52 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <88CA99A5-7D8B-49CA-831F-771326724507@gatech.edu>

On Thu, Jun 11, 2020 at 10:21 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> Just spitballing here…
>
> But what we could do is trap and then scan the next 1024 instruction in software and JIT to SimpleV.

it sounds reasonable enough to me.  could be done as a parallel
project in a simulator.

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] openpower virtual coffee now
From: Luke Kenneth Casson Leighton @ 2020-06-11 21:53 UTC (permalink / raw)
  To: Libre-RISCV General Development

7 minutes.
https://openpowerfoundation.org/openpower-virtual-coffee-calls/

_______________________________________________
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 374] New: add repo on github that points to git.libre-soc.org as a way to increase searchability
From: bugzilla-daemon @ 2020-06-11 22:17 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 374
           Summary: add repo on github that points to git.libre-soc.org as
                    a way to increase searchability
           Product: Libre-RISC-V Website
           Version: unspecified
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: website
          Assignee: lkcl@lkcl.net
          Reporter: programmerjake@gmail.com
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

-- 
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 374] add repo on github that points to git.libre-soc.org as a way to increase searchability
From: bugzilla-daemon @ 2020-06-11 22:19 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-374-13@https.bugs.libre-soc.org/>

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

Yehowshua <yimmanuel3@gatech.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yimmanuel3@gatech.edu

--- Comment #1 from Yehowshua <yimmanuel3@gatech.edu> ---
Interesting idea.
I had considered setting up a Github mirror to do this.
Alain or Luke would have to configure it to push.

Yehowshua

-- 
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 374] add repo on github that points to git.libre-soc.org as a way to increase searchability
From: bugzilla-daemon @ 2020-06-11 22:19 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-374-13@https.bugs.libre-soc.org/>

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

--- Comment #2 from Yehowshua <yimmanuel3@gatech.edu> ---
That is, our core repo on Libre-soc.org pushes to the Github mirror on every
commit.

-- 
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 374] add repo on github that points to git.libre-soc.org as a way to increase searchability
From: bugzilla-daemon @ 2020-06-11 22:47 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-374-13@https.bugs.libre-soc.org/>

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

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
the idea came up in the virtual coffee call today: it is for searchability,
to indicate the existence of the project.  a single file with a README
explaining that libre-soc is a Libre Project (not an "Open Source" one)
with a single link to the website would achieve this.

if the project's source code is actually mirrored *on* github, it indicates
an implicit endorsement by the project that proprietary services are
acceptable.

this GNU page explains the criteria:
https://www.gnu.org/software/repo-criteria.en.html

and this page evaluates commonly available and commonly used services:
https://www.gnu.org/software/repo-criteria-evaluation.html

of course we cannot prevent or prohibit *individuals* from utilising github:
that would be completely inappropriate, and the GNU project goes to some
lengths to explain how best to communicate that effectively and respectfully.

if however we wish to properly demonstrate a committment to ethical principles,
i.e. actually *be* a Libre Project, then respecting the GNU guidelines is
a good example to follow.

grey area: i am... "okay with" the idea of putting a single page README - not
in
any way under an "officially sanctioned" github username (registration of
github.com/libre-soc would be completely inappropriate) - under *personal*
github accounts, just to get at least something into github search criteria,
as long as it is just a single page, with a single link, and a short sentence
explaining that we are a Libre Project, following and respecting the GNU
Ethical Hosting guidelines.

-- 
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 374] add repo on github that points to git.libre-soc.org as a way to increase searchability
From: bugzilla-daemon @ 2020-06-11 22:48 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-374-13@https.bugs.libre-soc.org/>

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

--- Comment #4 from Jacob Lifshay <programmerjake@gmail.com> ---
If I recall correctly, Luke has an issue with hosting our code on GitHub since
that implies we're ok with GitHub being based on proprietary software.

I was thinking of creating a repo that only has a README.md file with links to
libre-soc

-- 
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 374] add repo on github that points to git.libre-soc.org as a way to increase searchability
From: bugzilla-daemon @ 2020-06-11 22:50 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-374-13@https.bugs.libre-soc.org/>

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

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Yehowshua from comment #2)
> That is, our core repo on Libre-soc.org pushes to the Github mirror on every
> commit.

sadly whilst very "convenient", this indicates that our project endorses
github's
unethical practices.  this includes censorship and government sanctioning.

https://sanctum.geek.nz/why-not-github.html

https://www.gnu.org/software/repo-criteria-evaluation.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 374] add repo on github that points to git.libre-soc.org as a way to increase searchability
From: bugzilla-daemon @ 2020-06-11 22:55 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-374-13@https.bugs.libre-soc.org/>

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

--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #4)
> If I recall correctly, Luke has an issue with hosting our code on GitHub
> since that implies we're ok with GitHub being based on proprietary software.

a decision was made for this to be an ethical (Libre) project, and for that
to actually mean what it says, rather than just use the word in a way that
leaves us open to accusations of being "Fake Libre" by people familiar with
the FSF and with the GNU project.

whether i *like* the inconvenience and the hassle that results from following
those ethical guidelines is an entirely different conversation! :)

> I was thinking of creating a repo that only has a README.md file with links
> to libre-soc

yeh, this, it is a "grey area".  i can see the sense in it, with people
searching
online - exclusively on github rather than just typing "libre-soc" into a wider
search engine - it would be good to at least have something that points them
here.

-- 
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 318] fix LDSTCompUnit
From: bugzilla-daemon @ 2020-06-11 22:58 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-318-13@https.bugs.libre-soc.org/>

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

--- Comment #24 from Cesar Strauss <cestrauss@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #22)
> the issue that needs looking at is to confirm that compldst_multi.py's
> unit tests are properly functional: i'm just not confident that they
> are.

Have yet to see the traces, but found this by inspection:

in load():

591        yield dut.rd.go.eq(rd)
592        yield from wait_for(dut.rd.rel)
593        yield dut.rd.go.eq(0)

This is backwards, I think. We wait for the CompUnit to assert rel, then we
send a one-clock pulse on the corresponding go.

I guess a solution is to simply wait on one rel signal at a time.

Eventually I'll come back to write the parallel test for this.

Meanwhile I'll take a look at the traces, see if I can catch anything.

-- 
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 374] add repo on github that points to git.libre-soc.org as a way to increase searchability
From: bugzilla-daemon @ 2020-06-11 23:00 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-374-13@https.bugs.libre-soc.org/>

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

--- Comment #7 from Yehowshua <yimmanuel3@gatech.edu> ---
> sadly whilst very "convenient", this indicates that our project endorses
> github's
> unethical practices.  this includes censorship and government sanctioning.

I disagree. Mirroring indicates that we do not endorse their practices.

But COLLABORATING on Github would be a different story.

And for that matter, I generally feel that Github has done a much better job at
handling open source than SourceForge did.
I generally try to maintain personal projects in such a way that migration away
from Github is possible and am careful with personal information.

-- 
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 374] add repo on github that points to git.libre-soc.org as a way to increase searchability
From: bugzilla-daemon @ 2020-06-11 23:01 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-374-13@https.bugs.libre-soc.org/>

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

--- Comment #8 from Jacob Lifshay <programmerjake@gmail.com> ---
if someone wants to create the readme file, I can put it on my github account,
which is probably the best one to use since I'm the one who's been part of
libre-soc the longest who has a github account

-- 
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 374] add repo on github that points to git.libre-soc.org as a way to increase searchability
From: bugzilla-daemon @ 2020-06-11 23:03 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-374-13@https.bugs.libre-soc.org/>

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

--- Comment #9 from Yehowshua <yimmanuel3@gatech.edu> ---
> if someone wants to create the readme file, I can put it on my github
> account, which is probably the best one to use since I'm the one who's been
> part of libre-soc the longest who has a github account

Sounds reasonable to me.

-- 
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 318] fix LDSTCompUnit
From: bugzilla-daemon @ 2020-06-11 23:22 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-318-13@https.bugs.libre-soc.org/>

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

--- Comment #25 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cesar Strauss from comment #24)
> (In reply to Luke Kenneth Casson Leighton from comment #22)
> > the issue that needs looking at is to confirm that compldst_multi.py's
> > unit tests are properly functional: i'm just not confident that they
> > are.
> 
> Have yet to see the traces, but found this by inspection:
> 
> in load():
> 
> 591        yield dut.rd.go.eq(rd)
> 592        yield from wait_for(dut.rd.rel)
> 593        yield dut.rd.go.eq(0)
> 
> This is backwards, I think.

it's simply broken, violating the protocol by potentially leaving the rd.go HI
for more than one cycle.  it needs to be

yield from waitfor(dut.rd.rel)
yield rd.go.eq(rd)
yield
yield rd.go.eq(0)

now it *may* be the case that by coincidence there is one clock in waitfor. 
that would give the correct ptotocol behaviour by accident.

> We wait for the CompUnit to assert rel, then we
> send a one-clock pulse on the corresponding go.

yes.

> 
> I guess a solution is to simply wait on one rel signal at a time.


except this would be a different type of test.


> 
> Eventually I'll come back to write the parallel test for this.

that would be fantastic.

> Meanwhile I'll take a look at the traces, see if I can catch anything.

you can see i caught an error where go signals are wired directly to rel
signals.

this trick will force an immediate response, in parallel, and there were a
number of corner cases in LDST and ALU CompUnits.

these turned out to be that the latch covering that particular go/req was
receiving a set *and* reset on the *same cycle*, and, with set taking priority,
the latch was left in the "set" position where it should have been dropped to
low.

even L0CacheBuffer had this exact same bug.  have a look at the last few git
diffs.

-- 
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 375] New: Finding new project members who can help with complex detailed work such as LDSTCompUnit
From: bugzilla-daemon @ 2020-06-11 23:40 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 375
           Summary: Finding new project members who can help with complex
                    detailed work such as LDSTCompUnit
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Conferences
          Assignee: lkcl@lkcl.net
          Reporter: colepoirier@gmail.com
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

I think it would very helpful if we had more project members who can help work
on the really complex pieces of the HDL, especially since Michael who has done
a very significant amount of this work, now, and I think for the next few
months(?) has less time to work on the project because he's writing his masters
thesis. Since I am not presently capable of helping with most of the HDL code,
especially the very complex pieces, I am willing to try and recruit more
people. Do you think this is a good idea? If so, do you have any suggestions as
to how I should go about 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] Fall 2022 Interfaces
From: Yehowshua @ 2020-06-12  2:59 UTC (permalink / raw)
  To: Libre-RISCV General Development

Was talking with Pine64 and Raptor about Fall2022 interfaces which I’m trying to finalize.
We can do everything including HDMI, ethernet, DDR4(via OpenCAPI OMI), and PCIE with SERDES lanes.

We need 10rx and 14tx SERDES.
4rx and 4tx for the OMI will need to run at 25GHz for DDR4 over OMI.
@Luke, is this possible for 45nm? Seems like it should be fine.

What type of expenses are we talking about for having Symbiotic EDA design the SERDES?

We’re going to need at least four different clock speeds - we will have to think about how to do this PLL wise - and down clock where possible.

https://libre-soc.org/45nm_Fall2022/?updated <https://libre-soc.org/45nm_Fall2022/?updated>

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] Fall 2022 Interfaces
From: Yehowshua @ 2020-06-12  3:00 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <E7F96DD9-4F42-4A32-B185-64279301CD5C@gatech.edu>


> Was talking with Pine64 and Raptor about Fall2022 interfaces which I’m trying to finalize.

Actually, wouldn’t say finalize so much as get a pretty good idea.
Things will obviously become more set in stone as we approach Fall 2022.

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] Fall 2022 Interfaces
From: Jacob Lifshay @ 2020-06-12  4:01 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <E7F96DD9-4F42-4A32-B185-64279301CD5C@gatech.edu>

On Thu, Jun 11, 2020, 19:59 Yehowshua <yimmanuel3@gatech.edu> wrote:

> Was talking with Pine64 and Raptor about Fall2022 interfaces which I’m
> trying to finalize.
> We can do everything including HDMI, ethernet, DDR4(via OpenCAPI OMI), and
> PCIE with SERDES lanes.
>

hdmi has issues with libre licensing and DRM content, if we're going that
fast, we should just go with display port or similar, since it's an open
standard, I think.


> We need 10rx and 14tx SERDES.
> 4rx and 4tx for the OMI will need to run at 25GHz for DDR4 over OMI.
>

25GHz seems *really* fast, probably impractically so unless going to *lots*
of effort, did you mean 2.5GHz?

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] Fall 2022 Interfaces
From: Cole Poirier @ 2020-06-12  4:33 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7fSit1+STs+WxMK4u2coY8GBnVgDw9mVjyq3VwUWdDDw@mail.gmail.com>


> On Jun 11, 2020, at 9:01 PM, Jacob Lifshay <programmerjake@gmail.com> wrote:
> 
> On Thu, Jun 11, 2020, 19:59 Yehowshua <yimmanuel3@gatech.edu> wrote:
> 
>> Was talking with Pine64 and Raptor about Fall2022 interfaces which I’m
>> trying to finalize.
>> We need 10rx and 14tx SERDES.
>> 4rx and 4tx for the OMI will need to run at 25GHz for DDR4 over OMI.
>> 
> 
> 25GHz seems *really* fast, probably impractically so unless going to *lots*
> of effort, did you mean 2.5GHz?

Maybe 25GB/s? “The OMI DDR4 Differential DIMM memory module supports a data throughput rate of 25.6GB/s with a latency of 40ns and densities up to 256GB. The new 84-pin DDR4 DDIMM is intended for use in standard server environments, using a serial interface and a differential Data Buffer (dDB) from Microchip. The DDIMM supports IBM’s P9 AIO and P10 processors’ memory attached architecture. The P9 AIO and P10 memory bus is defined with one read port and one write port per channel, each having eight unidirectional differential lanes supporting 25.6 Gbps data rate over the OMI direct attached to the DDIMM.”
https://www.eenewseurope.com/news/ddr4-differential-dimm-grows-opencapi-ecosystem

Still that’s for power 10 and late generation power 9 server processors.

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

* Re: [libre-riscv-dev] Fall 2022 Interfaces
From: Yehowshua @ 2020-06-12  5:46 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7fSit1+STs+WxMK4u2coY8GBnVgDw9mVjyq3VwUWdDDw@mail.gmail.com>

> 
> hdmi has issues with libre licensing and DRM content, if we're going that
> fast, we should just go with display port or similar, since it's an open
> standard, I think.

Perhaps - was reading Dave Shah’s convo on gitter…

He said Display Port is an absolute pain…

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

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