Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* Re: [libre-riscv-dev] HDL_Workflow clarification
From: Cole Poirier @ 2020-05-08 16:01 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDxG6AmN1t7B0f2qFSoOA_R0dK6OX6TQqGx7A+05tAa-rw@mail.gmail.com>

On May 8 2020, at 8:59 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> for people *not* doing coriolis2 there is no need to install in a chroot.
> 
> l.

Great. Thanks for the clarification.

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] HDL_Workflow clarification
From: Luke Kenneth Casson Leighton @ 2020-05-08 15:59 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <FF7FD0FA-6E07-4031-BD43-51DC2E6D9649@getmailspring.com>

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

On Fri, May 8, 2020 at 4:42 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
> I may be confused but it seems to me that the dependencies in the
> HDL_workflow such as softfloat, nmigen, symbiyosys, and our own soc reps
> should be installed inside the chroot set up at the end of section 6,
> but from the current state of the workflow on the wiki these are
> installed outside the chroot, before the chroot is even set up. My
> question is, should everything be inside of the chroot or just the
> alliance coriolis dependencies?

for people *not* doing coriolis2 there is no need to install in a chroot.

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] HDL_Workflow clarification
From: Cole Poirier @ 2020-05-08 15:42 UTC (permalink / raw)
  To: Libre-RISCV General Development

I may be confused but it seems to me that the dependencies in the
HDL_workflow such as softfloat, nmigen, symbiyosys, and our own soc reps
should be installed inside the chroot set up at the end of section 6,
but from the current state of the workflow on the wiki these are
installed outside the chroot, before the chroot is even set up. My
question is, should everything be inside of the chroot or just the
alliance coriolis dependencies?

Cole

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

^ permalink raw reply

* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-08 15:40 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>

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

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

> > Those 4 batches of Function Units are *completely separate*.  they do
> > *NOT* interact.
> Oh ok. So essentially we will have *separate* ports for the addition pipe,
> the multiplication pipe, the branch pipe, and instructions can be issued to
> each in parallel. 

yeeees :)

now you're getting it.

the DMs preserve the register-usage order and manage the regfile Buses.

the only "stalling" that's done is when the Issue stage cannot find a free
ReservationStation row to reserve for the instruction.

the output from the pipeline goes into the RS row "output" latch and sits
there until the FunctionUnit says "DMs say we have a free and clear path
to write to the regfile: go... like... go NOW".

the more regfile ports you have, the more results get written in parallel.

likewise for regfile reads for getting the operands *into* the RS Row(s).

-- 
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 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-08 15:35 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>

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

--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
src/soc/alu/pipe_data.py

will need to pass in everything and pass out everything.  carry-in as
well as carry-out.

the pipelines have to take *everything* that they need to produce a
result: they are not permitted to access global resources such as
regfiles.

this is why we have different FunctionUnits with totally different
specs() because for Branch it will take CTR and LR *as input*, where
for ALU it will take CR0 and a and b and so on

and for the MUL FU it will take about *four* possibly 5 inputs:
RA RB RC (for MAC) *and* carry-in *and* CR0 etc. etc.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-08 15:32 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>

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

--- Comment #5 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Michael Nolan from comment #3)

> 
> yes, with an "op" - which in our case will basically be "decoder.InternalOp"
> 

> 
> damnit this needs to be on the bugreport, i haven't got time, 10m until
> meeting
> 
> see page 8, diagram at the top.
> 
> Those 4 batches of Function Units are *completely separate*.  they do
> *NOT* interact.
Oh ok. So essentially we will have *separate* ports for the addition pipe, the
multiplication pipe, the branch pipe, and instructions can be issued to each in
parallel. 


> actually you know what, screw it: make separate ones for MUL and DIV,
> pretty much exactly like in that diagram on p8.  we're doing a
> radically different design as a proof-of-concept.
> 
> * add sub neg compare logical shift all go in their own
> Reservation-Station-style FunctionUnit
> * MUL in its own separate RS/FU
> * DIV likewise
yeah looks like it

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-08 15:29 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>

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

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
Created attachment 52
  --> https://bugs.libre-soc.org/attachment.cgi?id=52&action=edit
scoreboard mechanics image

michael can you drop this onto the wiki scoreboard page

-- 
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 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-08 15:29 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>

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

--- Comment #3 from Michael Nolan <mtnolan2640@gmail.com> ---
Luke's Reply:

On Fri, May 8, 2020 at 3:03 PM Michael N <mtnolan2640@gmail.com> wrote:

>> On May 8, 2020, at 9:28 AM, Michael Nolan <mtnolan2640@gmail.com> wrote:
>>
>> Now that I have branches working in the simulator, I was thinking of starting work on the integer ALU. Taking a look at alu_hier.py, I think I'll keep the interface but replace the implementation with a pipelined one.
>>
>> --Michael
>>
> I noticed alu_hier was nicely broken up into different function units (adder, branch unit, multiplier, etc.).

yes, with an "op" - which in our case will basically be "decoder.InternalOp"

> Is there a nice way you know of to do that with the nmutil pipeline stages?

yyyess.... except it's too complicated to explain right just this
minute.  raise the question in the bugreport.

> Like a way to merge stage 1 of the adder pipe with stage one of the branch pipe to get the stage 1 of the alu?

ok if you are talking about *outside* of ReservationStations, you are
mixing "purposes".  the Branch pipeline *does not* interact - at all -
with the ALU pipeline.

can you look again at Mitch's ScoreBoard Mechanics1.pdf

damnit this needs to be on the bugreport, i haven't got time, 10m until meeting

see page 8, diagram at the top.

Those 4 batches of Function Units are *completely separate*.  they do
*NOT* interact.

basically, the first ALU, do it entirely as combinatorial just as in
alu_hier.py and assume only one clock cycle.  leave out MUL and DIV
because those i believe need to be minimum 2 stages for MUL and a
*lot* for DIV.

actually you know what, screw it: make separate ones for MUL and DIV,
pretty much exactly like in that diagram on p8.  we're doing a
radically different design as a proof-of-concept.

* add sub neg compare logical shift all go in their own
Reservation-Station-style FunctionUnit
* MUL in its own separate RS/FU
* DIV likewise

l.

-- 
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 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-08 15:28 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>

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

--- Comment #2 from Michael Nolan <mtnolan2640@gmail.com> ---
From email:

I noticed alu_hier was nicely broken up into different function units (adder,
branch unit, multiplier, etc.). Is there a nice way you know of to do that with
the nmutil pipeline stages? Like a way to merge stage 1 of the adder pipe with
stage one of the branch pipe to get the stage 1 of the alu?

-- 
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 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-08 15:28 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lkcl@lkcl.net

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-May/006371.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

* Re: [libre-riscv-dev] daily kan-ban update 08mar2020
From: Luke Kenneth Casson Leighton @ 2020-05-08 15:27 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <825df4ef-1fe2-462e-aaeb-dd59e460ac88@gmail.com>

On Fri, May 8, 2020 at 4:22 PM Michael Nolan <mtnolan2640@gmail.com> wrote:

> Since runfp and ReservationStations use FPPipeContext, should it be
> moved to nmutil?

tck, tck... *thinks*... not now.  too much code involved (grep for how
many places the RS class is used, that's how many unit tests you'd
have to re-run)

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] Debug port (was Re:  minimum viable ASIC)
From: whygee @ 2020-05-08 15:27 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDw862-S1=Au1YbsKNy0629pa56eShp+2o_Avd96Auz8mw@mail.gmail.com>

On 2020-05-08 11:50, Luke Kenneth Casson Leighton wrote:
> i'd like to discuss what the minimum viable ASIC would look like,
> that, if we're happy to do so, we could hit the October 2020 deadline
> with it and not be completely stressed.
> 
<snip>
> 
> thoughts appreciated.

To me JTAG/TAP/debug port shine from its absence.

how will you "talk" with the chip when it
arrives from factory and you want to ensure
all its pins are correctly soldered/bonded
and you want to explore the insides to
test each unit ?

> l.
yg

_______________________________________________
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 08mar2020
From: Luke Kenneth Casson Leighton @ 2020-05-08 15:25 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <175BEA4F-5971-47BE-B5CE-2821BF430AE2@gmail.com>

On Fri, May 8, 2020 at 3:03 PM Michael N <mtnolan2640@gmail.com> wrote:

> > On May 8, 2020, at 9:28 AM, Michael Nolan <mtnolan2640@gmail.com> wrote:
> >
> > Now that I have branches working in the simulator, I was thinking of starting work on the integer ALU. Taking a look at alu_hier.py, I think I'll keep the interface but replace the implementation with a pipelined one.
> >
> > --Michael
> >
> I noticed alu_hier was nicely broken up into different function units (adder, branch unit, multiplier, etc.).

yes, with an "op" - which in our case will basically be "decoder.InternalOp"

> Is there a nice way you know of to do that with the nmutil pipeline stages?

yyyess.... except it's too complicated to explain right just this
minute.  raise the question in the bugreport.

> Like a way to merge stage 1 of the adder pipe with stage one of the branch pipe to get the stage 1 of the alu?

ok if you are talking about *outside* of ReservationStations, you are
mixing "purposes".  the Branch pipeline *does not* interact - at all -
with the ALU pipeline.

can you look again at Mitch's ScoreBoard Mechanics1.pdf

damnit this needs to be on the bugreport, i haven't got time, 10m until meeting

see page 8, diagram at the top.

Those 4 batches of Function Units are *completely separate*.  they do
*NOT* interact.

basically, the first ALU, do it entirely as combinatorial just as in
alu_hier.py and assume only one clock cycle.  leave out MUL and DIV
because those i believe need to be minimum 2 stages for MUL and a
*lot* for DIV.

actually you know what, screw it: make separate ones for MUL and DIV,
pretty much exactly like in that diagram on p8.  we're doing a
radically different design as a proof-of-concept.

* add sub neg compare logical shift all go in their own
Reservation-Station-style FunctionUnit
* MUL in its own separate RS/FU
* DIV likewise

l.

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

^ permalink raw reply

* Re: [libre-riscv-dev] daily kan-ban update 08mar2020
From: Michael Nolan @ 2020-05-08 15:21 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDwaffb9wvD7-Vg3ODfRdocVyLjf_qzBted-i_ZefL0wXA@mail.gmail.com>

On 5/8/20 11:10 AM, Luke Kenneth Casson Leighton wrote:
> yes please.  please raise a bugreport about it, assign it to yourself,
> and make certain to use the ReservationStations base class and test
> infrastructure (runfp) exactly as i described in here:
>
> https://bugs.libre-soc.org/show_bug.cgi?id=208#c55
>
> *all* ALUs need to have that common interface (multiple
> inputs-outputs).  if you can, use runfp - if there's any assumptions
> about the format being FP numbers, add an extra parameter which does
> debug printing as hexadecimal.  i *think* it should do that anyway
> because i used the same runfp test code for FP-to-INT and INT-to-FP
>
Since runfp and ReservationStations use FPPipeContext, should it be 
moved to nmutil?

--Michael


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

^ permalink raw reply

* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-08 15:17 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>

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

Michael Nolan <mtnolan2640@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|lkcl@lkcl.net               |mtnolan2640@gmail.com

-- 
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 305] New: Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-08 15:17 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 305
           Summary: Create Pipelined ALU similar to alu_hier.py
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Windows
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Source Code
          Assignee: lkcl@lkcl.net
          Reporter: mtnolan2640@gmail.com
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

From discussion with Luke:

an actual pipelined ALU, that expands on the alu_hier.py concept and
adds more functions - however it also needs to use PartitionedSignal.
this can default to "all off" initially.

Additionally, make certain to use the ReservationStations base class and test
infrastructure (runfp) exactly as i described in here:

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

*all* ALUs need to have that common interface (multiple
inputs-outputs).  if you can, use runfp - if there's any assumptions
about the format being FP numbers, add an extra parameter which does
debug printing as hexadecimal.  i *think* it should do that anyway
because i used the same runfp test code for FP-to-INT and INT-to-FP

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] daily kan-ban update 08mar2020
From: Luke Kenneth Casson Leighton @ 2020-05-08 15:16 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <F1BD2273-946B-4351-9695-7B2355A57DF3@gatech.edu>

On Fri, May 8, 2020 at 2:52 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> OK. Lemme have a go at this.

bugreport.  link to the interfaces page
https://libre-soc.org/180nm_Oct2020/interfaces/

> So I know we need LPC. Discussions with Raptor would have us use LPC to grab the boot loader externally I believe.

it's far more trivial even than that.  you literally set the Program
Counter to an address that is mapped to the LPC's memory-mapped
address.  that's it.  the Instruction Q fetch makes a request for an
instruction, that request goes over wishbone, wishbone directs it to
the LPC's memory-mapped peripheral, the LPC translates it into a "LPC
style memory request", the data comes back at that address.

it's so ridiculously not complicated it's actually "difficult to
understand why it's not more complicated".


> Here is some sample code for having the LCP sit as a wishbone slave.

ahh goooood.  perfect!

> Is Rudi on the mailing list yet?

no and i'm going to recommend he not be distracted by it.  define the
task, give him the task, and trust him to do it.  he's done massive
ASICs for some really large companies, multi-million-dollar work,
gigabit SERDES and last time i talked to him he was looking at doing a
USD $20m ASIC.

> https://gitlab.raptorengineering.com/raptor-engineering-public/lpc-spi-bridge-fpga/blob/master/lpc_interface.v#L1162 <https://gitlab.raptorengineering.com/raptor-engineering-public/lpc-spi-bridge-fpga/blob/master/lpc_interface.v#L1162>

_______________________________________________
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 08mar2020
From: Luke Kenneth Casson Leighton @ 2020-05-08 15:10 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <70a36b10-a95d-c956-03a0-c0c4dfda6f0d@gmail.com>

On Fri, May 8, 2020 at 2:28 PM Michael Nolan <mtnolan2640@gmail.com> wrote:
>
> Now that I have branches working in the simulator, I was thinking of
> starting work on the integer ALU. Taking a look at alu_hier.py, I think
> I'll keep the interface but replace the implementation with a pipelined
> one.

yes please.  please raise a bugreport about it, assign it to yourself,
and make certain to use the ReservationStations base class and test
infrastructure (runfp) exactly as i described in here:

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

*all* ALUs need to have that common interface (multiple
inputs-outputs).  if you can, use runfp - if there's any assumptions
about the format being FP numbers, add an extra parameter which does
debug printing as hexadecimal.  i *think* it should do that anyway
because i used the same runfp test code for FP-to-INT and INT-to-FP

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] Pinout, interfaces, Rudi, and Raptor
From: Luke Kenneth Casson Leighton @ 2020-05-08 15:03 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <3BD26F5C-BB6D-4011-89E6-EC06215DEDEA@gatech.edu>

On Fri, May 8, 2020 at 3:20 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> Hello Luke,
>         So I see we have some pinout sdefine here.
>
> https://libre-soc.org/shakti/m_class/pinouts/ <https://libre-soc.org/shakti/m_class/pinouts/>
>
>
> My suggestion is to drop the pinmux for now.

it needs writing anyway [not to use Bluespec].  that was *another*
project that took 3 months to do and we can't really use because it's
hard-coded to what the Shakti Team use in IIT Madras.  *sigh*.

> We should probably update that page(or create a similar page) to reflect what we’re targeting for October.

already done https://libre-soc.org/180nm_Oct2020/interfaces/


> IIRC, we’re targeting QFP. I don’t see the dimensions or form factor we’re targeting listed there however. We should talk about that.
>
> Also, talked with Tim and SDR could work for the first SBC.

update interfaces page https://libre-soc.org/180nm_Oct2020/interfaces/?updated

> LiteX also supports SDR which is good for us as it doesn’t require a PHY like DDR making it simpler.

yes.  and it's silicon-proven via the Shakti Team, in their first 22nm
ASIC from 2 years ago.


> Luke, should I connect Rudi to Tim?

hmmm.... in my mind, the roles do not really match up.  they do
however with one of us (by "us" i mean you :) given that i'm trying to
focus on heavily-technical development) as the intermediary

roles:

* Rudi's asked specifically for the interfaces, he'll write a spec as
a PDF and if we say "go" he'll get on with it.
* Tim's role here is as the "customer" plus he's busy.

therefore i suggest:

* *we* need to capture the requirements (of Tim) - by "we" i mean you
* go over them, discuss and approve them (whole team)
* *then* authorise Rudi to go ahead with a design document (i send the message)
* then go over that and discuss and review it (whole team)
* *then* notify Rudi "please go ahead" (i send the message)

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] minimum viable ASIC
From: Yehowshua @ 2020-05-08 15:00 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDw_Xzef6CFjZAa9+JktkN33NkvQTKMpo3U7VhfFwzRmSQ@mail.gmail.com>

> yep.  need peoples' help to do that, look for or create bugreports so
> the discussions don't go mad / all over the place.  i'm still really
> really trying to focus on this LD/ST interface before a call at 4:30pm
> today.

OK. I can put some effort into this. Please do stay focused.

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] minimum viable ASIC
From: Luke Kenneth Casson Leighton @ 2020-05-08 14:59 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <27527BBC-B545-4D85-A912-C90B7763070A@gatech.edu>

On Fri, May 8, 2020 at 1:59 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> Luke, I like the list of priorities. Can we convert it into a 15 week timeline?

yep.  need peoples' help to do that, look for or create bugreports so
the discussions don't go mad / all over the place.  i'm still really
really trying to focus on this LD/ST interface before a call at 4:30pm
today.

> We can use the timeline to inform where time/effort should be open. We should also pop the timeline on the wiki.

yes.

_______________________________________________
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 304] Define minimum viable interface set for 180nm ASIC
From: bugzilla-daemon @ 2020-05-08 14:37 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-304-13@https.bugs.libre-soc.org/>

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

Yehowshua <yimmanuel3@gatech.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|http://lists.libre-riscv.or |
                   |g/pipermail/libre-riscv-dev |
                   |/2020-May/006374.html       |

--- Comment #2 from Yehowshua <yimmanuel3@gatech.edu> ---
Relevant Links:

http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-May/006374.html
http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-May/006372.html
https://libre-soc.org/shakti/m_class/pinouts/
https://gitlab.raptorengineering.com/raptor-engineering-public/lpc-spi-bridge-fpga/tree/master

-- 
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 304] Define minimum viable interface set for 180nm ASIC
From: bugzilla-daemon @ 2020-05-08 14:36 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-304-13@https.bugs.libre-soc.org/>

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

Yehowshua <yimmanuel3@gatech.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yimmanuel3@gatech.edu
                URL|                            |http://lists.libre-riscv.or
                   |                            |g/pipermail/libre-riscv-dev
                   |                            |/2020-May/006374.html

--- Comment #1 from Yehowshua <yimmanuel3@gatech.edu> ---
Oh, my bad I'm just now seeing this.

Relea

-- 
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] Pinout, interfaces, Rudi, and Raptor
From: Yehowshua @ 2020-05-08 14:20 UTC (permalink / raw)
  To: Libre-RISCV General Development

Hello Luke,
	So I see we have some pinout sdefine here.

https://libre-soc.org/shakti/m_class/pinouts/ <https://libre-soc.org/shakti/m_class/pinouts/>


My suggestion is to drop the pinmux for now. We should probably update that page(or create a similar page) to reflect what we’re targeting for October.

IIRC, we’re targeting QFP. I don’t see the dimensions or form factor we’re targeting listed there however. We should talk about that.

Also, talked with Tim and SDR could work for the first SBC. LiteX also supports SDR which is good for us as it doesn’t require a PHY like DDR making it simpler.

Luke, should I connect Rudi to Tim?

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

^ permalink raw reply

* Re: [libre-riscv-dev] daily kan-ban update 08mar2020
From: Michael N @ 2020-05-08 14:03 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <70a36b10-a95d-c956-03a0-c0c4dfda6f0d@gmail.com>


> On May 8, 2020, at 9:28 AM, Michael Nolan <mtnolan2640@gmail.com> wrote:
> 
> Now that I have branches working in the simulator, I was thinking of starting work on the integer ALU. Taking a look at alu_hier.py, I think I'll keep the interface but replace the implementation with a pipelined one.
> 
> --Michael
> 
I noticed alu_hier was nicely broken up into different function units (adder, branch unit, multiplier, etc.). Is there a nice way you know of to do that with the nmutil pipeline stages? Like a way to merge stage 1 of the adder pipe with stage one of the branch pipe to get the stage 1 of the alu?

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

^ permalink raw reply

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