Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* Re: [libre-riscv-dev] Documenting the SOC tree Repository
From: Yehowshua @ 2020-05-03  0:08 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyMasGzb-jqu1nhrsddW0D4DNsAD0v100s17OMJ8-BhTA@mail.gmail.com>



> On May 2, 2020, at 7:24 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> 
> i really do not like branches. 

OK no branches. I’d like to move the CSVs to the soc repo, and then do an iframe to the git tree raw to display in the wiki.

I can wrap it in a little js to get the browser to render the csv as a table.

It doesn’t make sense to submodule the entire wiki in the SOC repo just for some tables. That’s structurally wrong.

Moving the CSVs directly into the SOC repo is low priority for me now - but, I’m just putting it out there - its something that needs to be addressed sooner than later.

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] Documenting the SOC tree Repository
From: Yehowshua @ 2020-05-03  0:09 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <6A20EC57-766F-4711-9233-785F162C1D3B@gatech.edu>

Apologies - this should have been in the big-tracker.

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] Documenting the SOC tree Repository
From: Luke Kenneth Casson Leighton @ 2020-05-03  0:21 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <6A20EC57-766F-4711-9233-785F162C1D3B@gatech.edu>

On Sunday, May 3, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

>
>
> > On May 2, 2020, at 7:24 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
> >
> > i really do not like branches.
>
> OK no branches


appreciated.


>  I’d like to move the CSVs to the soc repo, and then do an iframe to the
> git tree raw to display in the wiki.


a simpler proposal is to write a script that commits and copies the files
to the other (ikiwiki) repo.

some instructions can be placed in isatables indicating where the canonical
versions are (in soc).

however this again leaves


> I can wrap it in a little js to get the browser to render the csv as a
> table.


hm hm that makes js a hard dependency where it presently is not.

i wonder if the postcommit hook in ikiwiki could be modified to pretend
that the files are in the same repo.  the static html would then be built
still from the same source.


>
> It doesn’t make sense to submodule the entire wiki in the SOC repo just
> for some tables. That’s structurally wrong.


i honestly don't know the best option here.  duplication risks getting out
of sync.  all ootions have disadvantages


> Moving the CSVs directly into the SOC repo is low priority for me now -
> but, I’m just putting it out there - its something that needs to be
> addressed sooner than later.


the postcommit option i can ask alain if he can have a look.

l.



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


-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] experimental code & monorepo
From: Jacob Lifshay @ 2020-05-03  4:49 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <9458BF50-C9A6-44E5-AC7B-4A3891DE6CC1@gatech.edu>

On Sat, May 2, 2020, 11:47 Yehowshua <yimmanuel3@gatech.edu> wrote:

> Also - we have some experimental files in the SOC repo.
> I think it is a good practice to make an experimental branch instead.


> Thoughts?
>

We really should move all code that's not actually used in the final soc to
its own folder or branch -- currently, there is lots of unused code that
either was used in the past or we intend to eventually use or even never
intended to use (lots of minerva and some of the FP code) and was only ever
reference code to base our new code on. All of that makes it very confusing
to newcomers and partially confusing for people who aren't newcomers
anymore -- I myself couldn't point out with any degree of certainty all the
code that we actually intend to use even though I've been here longer than
nearly everyone else.

Additionally, I'd advocate for all HDL code (at least soc, ieee754fpu, and
nmutil) to be moved to one repo (especially including the data files
currently hosted on the wiki -- libre-soc.org shouldn't need to be
online/accessible to build if someone gets the git repos some other way)
and using submodules for often updated external dependencies (nmigen at
least), since that helps tie all the code together so one commit id is
sufficient to describe the state of all the code that's tightly
interconnected. See LLVM switching to a monorepo for an example of how this
is a good idea.

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] experimental code & monorepo
From: Luke Kenneth Casson Leighton @ 2020-05-03 11:02 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7fw-mX9F_cNwfZg_dBpoRP-YHBB9vWqHzPLqC--WkUvQ@mail.gmail.com>

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

On Sun, May 3, 2020 at 5:49 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Sat, May 2, 2020, 11:47 Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> > Also - we have some experimental files in the SOC repo.
> > I think it is a good practice to make an experimental branch instead.
>
>
> > Thoughts?
> >
>
> We really should move all code that's not actually used in the final soc to
> its own folder or branch -- currently, there is lots of unused code that
> either was used in the past or we intend to eventually use or even never
> intended to use

sigh this is because we were planning to use RISC-V and consequently,
planning ahead, developed and droppedin a ton of code *specifically*
intended to meet RISC-V MMU requirements for SMP cache-coherent
systems.

i've moved two directories into "unused".  a better name can be chosen later

> (lots of minerva

all of minerva

> and some of the FP code)

there definitely should not be *any* FP-related code in the soc repo.
this is deliberate at the moment


> and was only ever reference code to base our new code on.

no, the reason i dropped minerva into the tree was to *use* that code,
not to "base" our new code on.  definitely not as "reference code to
look at".  actually move or copy that code *out* of the minerva
subdirectory and *adapt* it.

to save a huge amount of time (which we do not have spare to write our
own code), this is still the plan for the entire L1 cache
infrastructure down to the wishbone interfaces, as outlined in the
bottom half of this diagram:

https://libre-soc.org/3d_gpu/180nm_single_core_testasic_memlayout.jpg


* modifying the L1 cache width to 128 bits,
* doubling them up (odd/even, addressable by addr[4]),
* splitting to dual 64-bit interfaces on the output (to meet Wishbone
requirements)
* and locating a suitable Wishbone Arbiter for the purpose of merging
the *four* resultant 64-bit interfaces onto the one 64-bit Wishbone
Bus.

the reason for doing this is as i said i think yesterday, is to save a
huge amount of time (which we *do not have spare*) and to make use of
the Minerva L1 Cache Formal Correctness Proof (which we likewise do
not have the time to replicate)

with no time left to add dual RISC-V support, other than support
modules for the L1 cache code (wishbone utils) the rest of the minerva
code can be discarded.


> All of that makes it very confusing
> to newcomers and partially confusing for people who aren't newcomers
> anymore -- I myself couldn't point out with any degree of certainty all the
> code that we actually intend to use even though I've been here longer than
> nearly everyone else.

you've been focussing on Kazan, which is great.

i _have_ been sending messages to the list (and also through the
bugtracker), describing what i'm doing (and why) - generally i do not
receive a response.

the reason for sending those messages was to give people an
opportunity to review and follow the code.  if people had responded
with questions, there would be less confusion right now because any
issues would have been cleared up at the time.

that said, i appreciate that it's complex code.

in effect, what we have here is: we're not really working together as
a team.  we're not collaborating: we're working in isolation on
separate components, very rarely interacting.

we're now seriously under time pressure: i count approximately 15
weeks before we have to begin the coriolis2 layout.

that's 15 weeks... *in which to complete the entire design*, by
approximately mid-august.

so we *have* to start working together, make as much use of
pre-existing code as possible, and cut some serious draconian corners
on what actually goes into the test chip.

i'd welcome some discussion on how to proceed here.


> Additionally, I'd advocate for all HDL code (at least soc, ieee754fpu, and
> nmutil) to be moved to one repo

see below

> (especially including the data files
> currently hosted on the wiki -- libre-soc.org shouldn't need to be
> online/accessible to build if someone gets the git repos some other way)

that's been changed (as intended, thank you michael) to use the git
submodule version rather than http get.  submodules has been a
nuisance (already) so i'm inclined to agree that not using them for
the .csv (and even the pseudocode .mdwn) is a good idea.

what to replace it with: there's no good options here.


> and using submodules for often updated external dependencies (nmigen at
> least),

the experience we've had - already - of using submodules is a royal
pain in the neck.  commits which involve changing of files *and*
changing submodules do *not* merge properly, and i actually had to use
rebase --skip for the first time - ever - in order to recover the
repository.  this lost some work by michael.

i'm inclined to suggest (as we discussed on the coriolis2 bug,
briefly) that an *independent* top-level repo be created that "joins"
*all* source code - and tools - together.  this to *never*, under any
circumstances, have actual files added to it (with the exception of a
README, saying "please read documentation at location X and please do
not edit this file further").

> since that helps tie all the code together so one commit id is
> sufficient to describe the state of all the code that's tightly
> interconnected. See LLVM switching to a monorepo for an example of how this
> is a good idea.

if the IEEE754 FP code had not been designed - from the start - to be
a general-purpose independent library and toolkit, i would agree
immediately with that.

however it was never intended - ever - right from the start - to be a
specific hard-coded isolated our-use-only FP library.  likewise
nmutil, by virtue of it mirroring the Chisel library from which we got
the Queue class.

this helped us to get additional funding and make the case for the
project being valuable *outside* of the scope of what we are doing, to
a wider community, and helps strengthen NLNet's role as a valuable
backer of Hardware/Software Libre.

nmutil then falls naturally into the category of being useful by
*both* repositories, and that's exactly as it's supposed to be.

all three are therefore actually independent projects.  putting their
source into a single repository has detrimental implications.  it also
results in confusion about what the roles of each of those three
independent projects is.

l.

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

^ permalink raw reply

* [libre-riscv-dev] [Bug 296] idea: cyclic buffer between FUs and register file
From: bugzilla-daemon @ 2020-05-03 11:58 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-296-13@https.bugs.libre-soc.org/>

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

--- Comment #12 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
hmm because we are aiming for a minimum 4x FP32 FMACs per cycle,
the datapath situation is much "worse" than i described earlier.
(meaning: the pressure to reduce the amount of control and information
wires is much higher).

* 4x FP32 FMACs is 2x 64-bit results
* however it's also 4x3 *read* registers @ FP32 which is 6x 64-bit
  reads.

having 6R2W on the regfile is completely impractical.

this is why we decided to go for the HI/LO-32-ODD/EVEN regfile split
(and to synchro-"pair" 32-bit operations if 64-bit calculations are
required, using PartitionedSignal).

by subdividing, we effectively end up with *four* separate isolated
32-bit-wide register files.

thus there will be *four* separate Common Data Buses, each serving
32-bit data to a *quarter* of the Function Units, each.

i'll draw it out.

-- 
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 296] idea: cyclic buffer between FUs and register file
From: bugzilla-daemon @ 2020-05-03 13:23 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-296-13@https.bugs.libre-soc.org/>

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

--- Comment #13 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://libre-soc.org/3d_gpu/architecture/regfile/

created a new page (for regfiles in general), it's a near-duplicate
of a very early diagram written out last year, except this time
the PartitionedSignal-baesd Pipelines, and Function Units, as well as
the cyclic buffers, are now included.

-- 
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 296] idea: cyclic buffer between FUs and register file
From: bugzilla-daemon @ 2020-05-03 14:07 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-296-13@https.bugs.libre-soc.org/>

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

--- Comment #14 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
i've updated the descriptive text at the page:
https://libre-soc.org/3d_gpu/architecture/regfile/

a review and commentary appreciated, so that architecturally this is
understood, and any potential errors and omissions detected.

-- 
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] Merging Repositories and Auto-Generating Static Documentation
From: Yehowshua @ 2020-05-04  2:13 UTC (permalink / raw)
  To: Libre-RISCV General Development

As Jacob mentioned earlier, I’m all in favor of merging nmutil, ieee754fpu <https://git.libre-soc.org/?p=ieee754fpu.git;a=summary>, and soc into one repository called soc.

Also, I’m working my way through the codebase and writing documentation. I strongly believe that the documentation should exist in the soc git repository itself so that anyone else who works with the docs only has to clone the git repository. This in fact seems fairly standard these days:

https://github.com/YosysHQ/nextpnr/tree/master/docs <https://github.com/YosysHQ/nextpnr/tree/master/docs>
https://github.com/SymbiFlow/prjtrellis/tree/master/docs <https://github.com/SymbiFlow/prjtrellis/tree/master/docs>
https://github.com/enjoy-digital/litex/tree/master/doc <https://github.com/enjoy-digital/litex/tree/master/doc>

If this is the case - it could be needlessly complex to try to pull these into the wiki directly. What we can do is have a static docs server at docs.libre-soc.org that builds upon every commit.

We can use python mkdocs or python sphinx or whatever.

This means that the wiki is not so much for documentation as it is for containing larger ideas about the Libre-SOC project itself.

Lastly, merging nmutil, ieee754fpu <https://git.libre-soc.org/?p=ieee754fpu.git;a=summary>, and soc into one repository called soc allows use to have one ./docs directory from which to build all documentation.

To merge these repositories is simple. Just copy ieee754fpu and nmutill into soc and modify the setup.py.

@Alain - how hard do you think it would be to setup a docs.libre-soc.org <http://docs.libre-soc.org/> subdomain?

Thoughts? Comments?

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] Merging Repositories and Auto-Generating Static Documentation
From: Luke Kenneth Casson Leighton @ 2020-05-04  8:33 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <84E08228-2EB8-441C-A022-C2151CDDE076@gatech.edu>

On Mon, May 4, 2020 at 3:13 AM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> As Jacob mentioned earlier, I’m all in favor of merging nmutil, ieee754fpu <https://git.libre-soc.org/?p=ieee754fpu.git;a=summary>, and soc into one repository called soc.

as i explained: this would unfortunately be a mistake that has
implications for NLNet, as well as sending a strong message that
nobody is welcome to use those independent libraries.

we need to focus on getting the code written.  reorganising the
codebase in this major way is a distraction.

> Thoughts? Comments?

we need to focus on developing the code.  this is a distraction.

we have only *fifteen weeks*.

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] Merging Repositories and Auto-Generating Static Documentation
From: Luke Kenneth Casson Leighton @ 2020-05-04  9:23 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwQgu0r+S7U0a_0zK-qaNXCeH_Jek66Gn4yd7XAT=9gTA@mail.gmail.com>

yehowshua: i understand the desire to reorganise because it gives you a
reason to go over everything, and thus crystallises the code in your mind
as working knowledge.

i really appreciate that you made the decision, several months ago, to help
with funding instead of coding as it is a critical step in the process.

however as we have only 15 weeks is the worst possie time to carry out
major reorganising.

it is a major distraction even to discuss this. i estimate it will be about
a WEEK to complete including rewriting all tutorials, automated scripts,
all of which critically depend on the repo structure.

alain is currently focussing on designing the ISA ready to present to
OpenPOWER.  he cannot afford the time to be distracted.  i had to stop
myself from asking him to do something else, even 30 minutes ago.

the critical priority need right now is *coding* in order to meet the
deadline.

can we please, everyone, focus on coding and on completing the tasks as
fast as possible.

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] global network of developers
From: Luke Kenneth Casson Leighton @ 2020-05-04  9:29 UTC (permalink / raw)
  To: Libre-RISCV General Development

very briefly, i have been contacted by a friend of a friend who has access
to emerging market and 3rd world software developers.

i have explained the urgency and also the conditions for NLNet funding.

i will keep people informed as to whether suitable developers are found.

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

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

--- Comment #32 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
jacob i've added documentation of the requirements of PortInterface:
https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=6404cf302734700514e7553bdf6c5a5df5badeb8

i'm doing a "dummy" one at the moment which will implement this API,
only allowing the one (and only one) Memory read/write per cycle.
this makes it clear exactly where the "merging" needs to take place.

putting the (twin/quad) L1 Caches in place once the L0CacheBuffer
has a single-cycle 128-bit-wide interface should be dead straightforward.

-- 
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] Merging Repositories and Auto-Generating Static Documentation
From: Luke Kenneth Casson Leighton @ 2020-05-04 12:59 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzSRkSFHBVnwyLnjua=Uwz9n5rQ4pCbiy-yw-3CCX7zPA@mail.gmail.com>

so is that clear, yehowshua, the detrimental implications to the
project if this decision were to go ahead?

i have been doing project time-management for a long time, always
thinking through the consequences of a decision, estimating completion
time fairly accurately, and we simply do not have the time to spare
(not even, really, to discuss it).  even Jean-Paul would be impacted
on the coriolis2 ASIC layout side because the changes result in him
having to change the way he supports us: his automated build scripts
would need updating to reflect changes to the repository structures.

with only 15 weeks left, we need people to knuckle down and get on
with the tasks, and regularly keep in touch about progress.  we don't
need extraneous non-essential tasks to be added to the list.

every extraneous non-essential task means that the functionality of
the ASIC has to be cut back even further from what has already been
removed.

does that help explain the consequences of what seems like an
otherwise simple and reasonable discussion?

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 300] New: Documentation for the SOC
From: bugzilla-daemon @ 2020-05-04 13:09 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 300
           Summary: Documentation for the SOC
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Mac OS
            Status: CONFIRMED
          Severity: minor
          Priority: ---
         Component: Source Code
          Assignee: lkcl@lkcl.net
          Reporter: yimmanuel3@gatech.edu
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

The SOC would benefit from good documentation.
The wiki is likely not the appropriate place to host documentation.

It seems a number of open source projects host documentation on a static site
which build from a ./docs folder in the git repository.

https://github.com/YosysHQ/nextpnr/tree/master/docs 
https://github.com/SymbiFlow/prjtrellis/tree/master/docs 
https://github.com/enjoy-digital/litex/tree/master/doc

LibreSOC would benefit from following this convention.
To accomplish this, a gitlab ci.yaml can be placed in the ./docs directory of
soc.git. This way,  it is at least possible to view documentation at
Kazan-team.salsa.debian.io/docs. The documentation's bootstrap can also be
modified to match libreSOC’s main site.

It is probably fine to link to salsa from the wiki for now. We can always bring
the static site directly onto libreSOC’s servers later.

-- 
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] Merging Repositories and Auto-Generating Static Documentation
From: Yehowshua @ 2020-05-04 13:10 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDw8ppVRgVA93Ty746_928uCJb110zV-Qp5KJJojY-1Skg@mail.gmail.com>

> so is that clear, yehowshua, the detrimental implications to the
> project if this decision were to go ahead?

Given we only have 4 people working on the bulk at the moment - the need to accelerate without impediment is clear. We can always circle back to this later.

For now, I have raised a bug report for the documentation.

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

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

^ permalink raw reply

* [libre-riscv-dev] [Bug 300] Documentation for the SOC
From: bugzilla-daemon @ 2020-05-04 13:12 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-300-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Yehowshua from comment #0)
> The SOC would benefit from good documentation.
> The wiki is likely not the appropriate place to host documentation.
> 
> It seems a number of open source projects host documentation on a static
> site which build from a ./docs folder in the git repository.


> https://github.com/YosysHQ/nextpnr/tree/master/docs 
> https://github.com/SymbiFlow/prjtrellis/tree/master/docs 
> https://github.com/enjoy-digital/litex/tree/master/doc

this is because they are hosted on github.

> LibreSOC would benefit from following this convention.
> To accomplish this, a gitlab ci.yaml can be placed in the ./docs directory
> of soc.git. This way,  it is at least possible to view documentation at
> Kazan-team.salsa.debian.io/docs. The documentation's bootstrap can also be
> modified to match libreSOC’s main site.

salsa is not under our control.

> It is probably fine to link to salsa from the wiki for now. We can always
> bring the static site directly onto libreSOC’s servers later.

we do not have time to discuss this right now.

the priority is to complete the tasks for the hard deadline.

closing this bugreport to indicate that we need to seriously prioritise
and not discuss extraneous non-critical tasks.

it can be re-opened when we have 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

* Re: [libre-riscv-dev] Merging Repositories and Auto-Generating Static Documentation
From: Luke Kenneth Casson Leighton @ 2020-05-04 13:14 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <D100D780-073D-4969-AB0D-E53C72DC9C64@gatech.edu>

On Mon, May 4, 2020 at 2:10 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> > so is that clear, yehowshua, the detrimental implications to the
> > project if this decision were to go ahead?
>
> Given we only have 4 people working on the bulk at the moment - the need to accelerate without impediment is clear. We can always circle back to this later.
>
> For now, I have raised a bug report for the documentation.

appreciated.  i've closed it to indicate the seriousness of the need
to focus and get the tasks done as the absolute critical top priority.

l.

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

^ permalink raw reply

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

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

--- Comment #33 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
okaaay, it's messy but functional, and, importantly, illustrates the API,
jacob.

i've not put in actual LD/ST width yet, so the tests "pass" based on storing
a 16-bit value into a hard-coded-16-bit-wide "Memory", the important thing
is the signalling and API conformance, illustrating the timing that's
required (and expected) by LDSTCompUnit.

at least this allows me to move on to the (new, ridiculously-redrawn)
LDSTCompUnit.

we'll need to coordinate when it comes to adding twin ports (for misaligned)
however it may just be ok there to assume the misaligned port is never
used by LDSTCompUnit as the 2nd port is being added to L0CacheBuffer, get
the unit tests working for L0CacheBuffer, then add it to LDSTCompUnit, and
*then* add unit tests to LDSTCompUnit that try using 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] daily status update 05may2020
From: Luke Kenneth Casson Leighton @ 2020-05-05 10:47 UTC (permalink / raw)
  To: Libre-RISCV General Development

i'm going to start doing daily status updates on the list,
"kanban-style".  it would be good if everyone else did as well, as we
can keep in touch and see what's going on.

yesterday i got the preliminary / testing L0CacheBuffer up and
running: the important bit being the PortInterface class which
connects to the LD/ST Computational Units.

today i'll be working on the redesigned LD/ST Computational Unit which
has 3R-2W (indexed and update) capability.
https://libre-soc.org/3d_gpu/ld_st_comp_unit.jpg

the L0CacheBuffer is on the critical path even for testing of the
LDSTCompUnit, because there are several LDSTCompUnits, all connecting
to the (one) L0CacheBuffer.

that's it.  what is everyone else doing?

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] global network of developers
From: Luke Kenneth Casson Leighton @ 2020-05-05 11:09 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzZAneZcBwROdCVQVB6E6aqOJh9TCnYSW1M-Yyqr4bU7w@mail.gmail.com>

On Mon, May 4, 2020 at 10:29 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:

> very briefly, i have been contacted by a friend of a friend who has access to emerging market and 3rd world software developers.
>
> i have explained the urgency and also the conditions for NLNet funding.

... which because they have a Foundation in place (MarketNext
Foundation) is not a problem.  NLNet can transfer funds to that
Foundation, that Foundation can take care of distributing donations in
exchange for work done.

> i will keep people informed as to whether suitable developers are found.

i found out today a bit more about them: https://marketnext.org/what-we-do-3/

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] global network of developers
From: Luke Kenneth Casson Leighton @ 2020-05-05 12:51 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwUvRqWHvN6AjuWVeCNk76HZ65FwmVth__gf3XxqWe0OA@mail.gmail.com>

the MarketNext Foundation would like to do an article in their
newsletter, and also to do a webinar in order to present the project
to their Members, so that Members can get in touch and select tasks to
complete.  i'd like everyone to have the opportunity to participate in
those.  more when i have more info.

l.

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

^ permalink raw reply

* Re: [libre-riscv-dev] daily status update 05may2020
From: Yehowshua @ 2020-05-05 13:02 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwbe8bVrqR9OpBYR-Xfp-K7XGi=YStbuF-s8jwU2z1O6w@mail.gmail.com>



> On May 5, 2020, at 6:47 AM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> 
> yesterday i got the preliminary / testing L0CacheBuffer up and
> running:

Great!

> the important bit being the PortInterface class which
> connects to the LD/ST Computational Units.
> 

What exactly is a LDSTCompUnit? A cursory Google search just brings up Libre-SOC.
Does it take a LD/ST instruction and compute the offset before access?

Why do you call it cache buffer - I’ve only heard the term cache.

Also, how many ways is the cache? Is it configureable - are you pulling in the source from minerva?

> today i'll be working on the redesigned LD/ST Computational Unit which
> has 3R-2W (indexed and update) capability.
> https://libre-soc.org/3d_gpu/ld_st_comp_unit.jpg <https://libre-soc.org/3d_gpu/ld_st_comp_unit.jpg>
Can we have a link to the gittree for this code.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] daily status update 05may2020
From: Yehowshua @ 2020-05-05 13:07 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwbe8bVrqR9OpBYR-Xfp-K7XGi=YStbuF-s8jwU2z1O6w@mail.gmail.com>



> On May 5, 2020, at 6:47 AM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> 
> it would be good if everyone else did as well, as we
> can keep in touch and see what's going on.

I’m working my way through the codebase and slowly adding documentation.

I was hired by Georgia Tech to revise critical parts of the Computer Architecture curriculum and I have to write my Thesis this summer - about 14 hours a day - so yeah - slowly documenting.

Talking to some lawyers about bringing in the Libre-SOC and Kazan trademarks under Systèmes Libres.

Also, discussing equity. Individuals who made contributions to Libre-SOC in the past and who continue to make contributions until seed-funding of Systèmes Libres are eligible for equity according to the Slicing Pie model.

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] global network of developers
From: Yehowshua @ 2020-05-05 13:10 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwUvRqWHvN6AjuWVeCNk76HZ65FwmVth__gf3XxqWe0OA@mail.gmail.com>



> On May 5, 2020, at 7:09 AM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> 
> i found out today a bit more about them: https://marketnext.org/what-we-do-3/ <https://marketnext.org/what-we-do-3/>

This is quite exciting. Would NLNet be paying them from funding currently reserved for parts of the Libre-Soc project?

Also, I’d really hope that MarketNext can put us in touch with grad students - we do need skilled labor.

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