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

* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-08 16:48 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 #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #4)
> Created attachment 52 [details]
> scoreboard mechanics image
> 
> michael can you drop this onto the wiki scoreboard page

thank you.  meeting still not happened yet, waiting for a call, did
a quick section and also added the corresponding write diagram
https://libre-soc.org/3d_gpu/architecture/6600scoreboard/?updated

so just to emphasise, michael: for ALUInitialData it will need:

+class ALUInitialData(IntegerData):
+    def __init__(self, pspec):
+        super().__init__(pspec)
+        self.a = Signal(64, reset_less=True)
+        self.b = Signal(64, reset_less=True)

plus XER carry-in as an input operand and also the opcode itself.
although... that's going to be in ctx, as opkls?  hmm... see separate
comment

and a *separate* output class (not the same as ALUInitialData)
will be needed with:

* output result (RT)
* CA CA32
* CR0
* SO OV OV32

-- 
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 16:54 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 #9 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
there's a bit of a nuisance... no there isn't, you're good.
FPPipeContext contains the muxid (which the ReservationStation
uses as an array index).  you got it right by passing in
CompAlUOpSubset as the opkls.

-- 
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] Debug port (was Re: minimum viable ASIC)
From: Luke Kenneth Casson Leighton @ 2020-05-08 16:55 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <9191058ea0912f2b508a6f73ea567e5f@f-cpu.org>

On Fri, May 8, 2020 at 4:27 PM <whygee@f-cpu.org> wrote:

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

yep good catch.  added.


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 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-08 17:04 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 #10 from Michael Nolan <mtnolan2640@gmail.com> ---
Does it make sense to have the ALU inputs a and b be PartitionedSignals?

-- 
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 17:10 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 #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #10)
> Does it make sense to have the ALU inputs a and b be PartitionedSignals?

later.  not right now.  if we have time we convert them to PartitionedSignals.

-- 
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] Debug port (was Re: minimum viable ASIC)
From: Staf Verhaegen @ 2020-05-08 17:23 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDzdkhVJuJ3_UqZTbd7i7vXJ5iiu3qz+LUBsFRJrzCcEmQ@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 355 bytes --]

Luke Kenneth Casson Leighton schreef op vr 08-05-2020 om 17:55 [+0100]:
> On Fri, May 8, 2020 at 4:27 PM <whygee@f-cpu.org> wrote:
> > To me JTAG/TAP/debug port shine from its absence.
> 
> yep good catch.  added.

I already have (alpha version) nmigen JTAG code: https://gitlab.com/Chips4Makers/c4m-jtagStaf. id="-x-evo-selection-start-marker">


[-- Attachment #2: Type: text/plain, Size: 177 bytes --]

_______________________________________________
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: Staf Verhaegen @ 2020-05-08 17:25 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDw+m3B-7eLOqYBVccTBzED9hbtAwftDdcBR2nZRmuES5w@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 257 bytes --]

Luke Kenneth Casson Leighton schreef op vr 08-05-2020 om 11:59 [+0100]:
> writing on behalf of these two people:
> 
> Staf is doing a 180nm tapeout for the next few days.

Staf is doing the 180nm NLNet test vehicle tape-out for the next few days :)


[-- Attachment #2: Type: text/plain, Size: 177 bytes --]

_______________________________________________
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 18:38 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 #12 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #11)
> (In reply to Michael Nolan from comment #10)
> > Does it make sense to have the ALU inputs a and b be PartitionedSignals?
> 
> later.  not right now.  if we have time we convert them to
> PartitionedSignals.

i know :)  we did all that work and we need to focus first on a
scalar version.  it means not needing to fuss about parallel-masked
decisions and so on, which i am expecting shouuuld make development
time faster.

-- 
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] minimum viable ASIC
From: Staf Verhaegen @ 2020-05-08 19:08 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDwCrPLonpnn6WapzLyeYkgCy9c7NoZM+HoVb6uaZ1J-Yw@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 987 bytes --]

Luke Kenneth Casson Leighton schreef op vr 08-05-2020 om 13:46 [+0100]:
> On Fri, May 8, 2020 at 1:44 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
> > I talked to Raptor and if Series A doesn’t pan out in August, Raptor is willing to foot 30k for PLL design in exchange for some equity.
> 
> that's fantastic.  it would give us (and any other team)Foundry-independence.  normally the PLL is available as a StandardCell from a Foundry... but only under NDA.

Be aware that PLL is an analog block meaning that if you let it design for a certain process from a certain foundry it will only work for that node and foundry. It is not portable like RTL code is unless specifically designed for that but analog designers typically don't know how to do that. Also in order to design the PLL you need NDA to access the PDK which likely also forbids making the final GDSII of your design public.

Also giving away equity gives cause for other type of dependence...

greets,
Staf.



[-- Attachment #2: Type: text/plain, Size: 177 bytes --]

_______________________________________________
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] note on memory operation requirements for linux
From: Jacob Lifshay @ 2020-05-08 19:15 UTC (permalink / raw)
  To: Libre-RISCV General Development

I haven't checked but I'm 99% sure that we will need to implement standard
Power atomics, fences, ll/sc (including 128-bit version), cache flushes,
and non-cacheable load/store operations if we want to support Linux on our
october test chip.

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 08mar2020
From: Yehowshua @ 2020-05-08 20:27 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDw-nM8HiGuMaSZPsvf0HBJCCpAfRQjJJOpUZce7uiBOrQ@mail.gmail.com>

Today I worked on legal things.
Also put a rough sketch together for the minimum number of interfaces we need to support.

I put USB and ethernet at second priority. I talked with Florent from EnjoyDigital, and while LiteX supports USB, it may require some non-trivial modification on our part if we didn’t want to go with (FTDI or Cypress) chips which I think max out at 200MB/s.

He pointed me to some alternatives in both Migen and nMigen:
- https://github.com/im-tomu/valentyusb <https://github.com/im-tomu/valentyusb>
- https://github.com/lambdaconcept/lambdaUSB <https://github.com/lambdaconcept/lambdaUSB>
- https://github.com/greatscottgadgets/luna <https://github.com/greatscottgadgets/luna>

I’ll pop them on the Wiki.

Litex also support ethernet which would require a $20 PHY, not great for a low cost SBC. We could also do ethernet over USB - this would render the boot loader slightly more complex if we wished to use ethernet during the boatloader.

Again, ethernet is not **essential for a minimum viable ASIC.

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 20:35 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <8a9513e929732def9055bf6ec09da2deeea3f794.camel@fibraservi.eu>

On Fri, May 8, 2020 at 8:08 PM Staf Verhaegen <staf@fibraservi.eu> wrote:
>
> Luke Kenneth Casson Leighton schreef op vr 08-05-2020 om 13:46 [+0100]:
> > On Fri, May 8, 2020 at 1:44 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
> > > I talked to Raptor and if Series A doesn’t pan out in August, Raptor is willing to foot 30k for PLL design in exchange for some equity.
> >
> > that's fantastic.  it would give us (and any other team)Foundry-independence.  normally the PLL is available as a StandardCell from a Foundry... but only under NDA.
>
> Be aware that PLL is an analog block meaning that if you let it design
> for a certain process from a certain foundry it will only work for that node and foundry.

yes.

> It is not portable like RTL code is unless specifically designed for that but
> analog designers typically don't know how to do that.

the professor at LIP6.fr knows what he is doing.

> Also in order to design the PLL you need NDA to access the PDK which likely
> also forbids making the final GDSII of your design public.

yes, have to be realistic about that.

thanks Staf.

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] daily kan-ban update 08mar2020
From: Alain D D Williams @ 2020-05-08 20:38 UTC (permalink / raw)
  To: Libre-RISCV General Development

Today I did some work installing a new web server for another customer.

Not as much done as I hoped ... my neighbours organised a social distancing
street party as today is a UK public holiday to celebrate VE day (end of the 2nd
world war)

-- 
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256  https://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html
#include <std_disclaimer.h>

_______________________________________________
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 20:47 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDxBon96+0GaFutee0JHoqGw_m07aEQAE7CF21rjBoMqHA@mail.gmail.com>

On 5/8/20 11:25 AM, Luke Kenneth Casson Leighton wrote:
> 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.

I think I made some decent progress on this. I implemented a couple 
instructions in the ALU, and wrote both formal proofs for what I expect 
the ALU stages to do, as well as a test that compares the output of the 
alu from the output of the power_pseudo simulator.

--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

* Re: [libre-riscv-dev] daily kan-ban update 08mar2020
From: Luke Kenneth Casson Leighton @ 2020-05-08 20:47 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <20200508203816.GJ4924@phcomp.co.uk>

On Fri, May 8, 2020 at 9:38 PM Alain D D Williams <addw@phcomp.co.uk> wrote:
>
> Today I did some work installing a new web server for another customer.
>
> Not as much done as I hoped ... my neighbours organised a social distancing
> street party as today is a UK public holiday to celebrate VE day (end of the 2nd
> world war)

ah that would explain the red-white-blue bunting on a neighbour's
house - something i haven't seen since Queen Elizabeth's Jubilee in
1977 :)

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: Jacob Lifshay @ 2020-05-08 21:39 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <D311CF96-8F97-4D2C-8D36-B85532F0D4A5@gatech.edu>

On Fri, May 8, 2020, 13:27 Yehowshua <yimmanuel3@gatech.edu> wrote:

> Litex also support ethernet which would require a $20 PHY, not great for a
> low cost SBC.


There are some inexpensive GbE PHYs using the GMII interface (what I think
is what we are planning on using), mouser sells some for less than $2 each:
https://www.mouser.com/ProductDetail/Intel/PEF7072HLV16-S-LLHN?qs=d5w0Orft5TofEDXuIkwIvA==

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] Debug port (was Re: minimum viable ASIC)
From: Luke Kenneth Casson Leighton @ 2020-05-08 22:19 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <63e8b9ce54648590e2a6fc51bc2110dde7585f5e.camel@fibraservi.eu>

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

On Fri, May 8, 2020 at 6:23 PM Staf Verhaegen <staf@fibraservi.eu> wrote:
>
> Luke Kenneth Casson Leighton schreef op vr 08-05-2020 om 17:55 [+0100]:
> > On Fri, May 8, 2020 at 4:27 PM <whygee@f-cpu.org> wrote:
> > > To me JTAG/TAP/debug port shine from its absence.
> >
> > yep good catch.  added.
>
> I already have (alpha version) nmigen JTAG code: https://gitlab.com/Chips4Makers/c4m-jtag
> Staf. id="-x-evo-selection-start-marker">

found the link (minus HTML error)
https://gitlab.com/Chips4Makers/c4m-jtag

ah.  as a software engineer, the practice of using wildcard imports is
an extremely bad one.  i strongly advocate *not* getting into the
habit of doing "from nmigen import *" everywhere - it will make your
life - and other users lives - absolute hell when it comes to trying
to track and debug code.

minerva has a JTAG interface as well.  i corrected the practice of
using "import *" in this one

https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/minerva/units/debug/controller.py;h=7304303e577b14eebba15144642eb7bee829e107;hb=a54adcb65bad37b398b11e33a824c7d08c5fe509

it looks like the minerva team got a long way with that.  also
provided a wishbone master interface:

https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/minerva/units/debug/wbmaster.py;h=db02af95b4eb3ef8ac25b348f3abaa2bcbe7d96f;hb=a54adcb65bad37b398b11e33a824c7d08c5fe509

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: Luke Kenneth Casson Leighton @ 2020-05-08 22:23 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <463a58f7e45cf64feaafa9f62d94a3be4d397258.camel@fibraservi.eu>

On Fri, May 8, 2020 at 6:25 PM Staf Verhaegen <staf@fibraservi.eu> wrote:
>
> Luke Kenneth Casson Leighton schreef op vr 08-05-2020 om 11:59 [+0100]:
> > writing on behalf of these two people:
> >
> > Staf is doing a 180nm tapeout for the next few days.
>
> Staf is doing the 180nm NLNet test vehicle tape-out for the next few days :)

oh right!  i thought that was for March, not May :)

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 08may2020
From: Jacob Lifshay @ 2020-05-08 22:34 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD62Q1TOCooXhJ-VsvJTgY4+adnchjoqe9jFtK+r9qRTeQ@mail.gmail.com>

(Fixed the title, it's may not march.)

still working on load/store unit, though likely won't progress that far
since Fridays are more like 1/2 a work day for me due to religious reasons
(sabbath going from sundown every friday to sundown every saturday) as well
as me starting the day a little later than I probably should.

yehowshua, I noticed you like math, if you have some free time you might
find some of the algorithms in the algebraics library I wrote interesting
since it's a lot of number theory and modular arithmetic. Yay for factoring
polynomials over modular integers!! (glad I don't have to figure that out
again)

https://docs.rs/algebraics/0.2.0/algebraics/polynomial/struct.Polynomial.html#method.factor

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 08mar2020
From: Luke Kenneth Casson Leighton @ 2020-05-08 22:41 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <D311CF96-8F97-4D2C-8D36-B85532F0D4A5@gatech.edu>

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

On Fri, May 8, 2020 at 9:27 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> Today I worked on legal things.
> Also put a rough sketch together for the minimum number of interfaces we need to support.
>
> I put USB and ethernet at second priority.

good.

> I talked with Florent from EnjoyDigital, and while LiteX supports USB, it may require some non-trivial modification on our part if we didn’t want to go with (FTDI or Cypress) chips which I think max out at 200MB/s.
>
> He pointed me to some alternatives in both Migen and nMigen:
> - https://github.com/im-tomu/valentyusb <https://github.com/im-tomu/valentyusb>
> - https://github.com/lambdaconcept/lambdaUSB <https://github.com/lambdaconcept/lambdaUSB>

right.  this one is ULPI (not USB)
https://github.com/lambdaconcept/lambdaUSB/blob/master/lambdausb/phy/ulpi.py

this one (and the corresponding rx.py) i'm not quite understanding the context
https://github.com/lambdaconcept/lambdaUSB/blob/master/lambdausb/phy/usb/tx.py


> - https://github.com/greatscottgadgets/luna <https://github.com/greatscottgadgets/luna>
>
> I’ll pop them on the Wiki.

use this:
https://libre-soc.org/shakti/m_class/USB2

or this as appropriate, depending on whether they're *actual* USB2
(which is unlikely given that it needs to be analog) or whether they
are UMTI / ULPI.
https://libre-soc.org/shakti/m_class/ULPI/ is the "parallel bus"
version - it does however need cross-referencing to the USB2 page.

i suspect that they're all ULPI... i *hope* they're not ohhh right,
FTDI.  that's almost certainly a "serial bus" (like the FT232 only a
bit faster).

basically UMTI is great (but a lot of pins), ULPI is better (needs
DDR), but *actual* USB2 (D+ and D-) requires a complex analog design.



> Litex also support ethernet which would require a $20 PHY, not great for a low cost SBC.

oink.  the RTL8192 RGMII PHY is under USD $1.  what the hell are they
doing picking a $20 PHY??

there's plenty of RGMII opencores / open cores out there, and the
litex eth looks like it supports a range:
https://github.com/enjoy-digital/liteeth/tree/master/liteeth/phy

GMII, MII, RMII but interestingly not RGMII (reduced gigabit MII).
RGMII is double-data-rate and half the bits (4 per tx, 4 per rx)

ok https://github.com/enjoy-digital/liteeth/blob/master/liteeth/phy/ecp5rgmii.py




> We could also do ethernet over USB - this would render the boot loader slightly more complex if we wished to use ethernet during the boatloader.

no, definitely not.  far too complex (booting over ethernet) and
having to initialise the USB controller as well?  no.  see dan
gisselquist's code and how much work was involved.

the typical ROM size is 8k to 16k.  that's *it*.

if you *really* have a need to boot over ethernet or over USB, it
should be done as a 2nd-stage boot chain.


> Again, ethernet is not **essential for a minimum viable ASIC.

nope it's not.

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: Luke Kenneth Casson Leighton @ 2020-05-08 22:45 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD62Q1TOCooXhJ-VsvJTgY4+adnchjoqe9jFtK+r9qRTeQ@mail.gmail.com>

On Fri, May 8, 2020 at 10:39 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Fri, May 8, 2020, 13:27 Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> > Litex also support ethernet which would require a $20 PHY, not great for a
> > low cost SBC.
>
>
> There are some inexpensive GbE PHYs using the GMII interface (what I think
> is what we are planning on using),

RGMII.  GMII is 8-bit TX, 8-bit RX (so around 26 pins total) where
RGMII is DDR and half the TX and RX pins.  you can see here
https://libre-soc.org/shakti/m_class/pinouts/


> mouser sells some for less than $2 each:
> https://www.mouser.com/ProductDetail/Intel/PEF7072HLV16-S-LLHN?qs=d5w0Orft5TofEDXuIkwIvA==

which  means in China it's well under $1

RT8192.

an alternative is an MCU Bus (AT/XT/ISA) and to use the DM9000.

https://libre-soc.org/shakti/m_class/peripheralschematics/

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: Luke Kenneth Casson Leighton @ 2020-05-08 22:48 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <092fd357-7727-b191-826b-9e920d654f58@gmail.com>

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

> I think I made some decent progress on this. I implemented a couple
> instructions in the ALU, and wrote both formal proofs for what I expect
> the ALU stages to do, as well as a test that compares the output of the
> alu from the output of the power_pseudo simulator.

nice.

l.

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

^ permalink raw reply

* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-08 23:08 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 #13 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
this:

        # If there's an immediate, set the B operand to that
        with m.If(self.i.ctx.op.imm_data.imm_ok):
            comb += self.o.b.eq(self.i.ctx.op.imm_data.imm)
        with m.Else():
            comb += self.o.b.eq(self.i.b)

...is already done by the Computation Unit:

        # select immediate if opcode says so.  however also change the latch
        # to trigger *from* the opcode latch instead.
        op_is_imm = oper_r.imm_data.imm_ok
        src2_or_imm = Signal(self.rwid, reset_less=True)
        src_sel = Signal(reset_less=True)
        m.d.comb += src_sel.eq(Mux(op_is_imm, opc_l.q, src_l.q[1]))
        m.d.comb += src2_or_imm.eq(Mux(op_is_imm, oper_r.imm_data.imm,
                                                  self.src2_i))

there is *not* supposed to be a relationship between "register numbers"
and "Function Unit Operands".  Function Units are not permitted to know
about registers, at all (however by a coincidence we happen to be
preserving the order, RA = operand1, RB = operand2 etc).

however... i quite like that it's possible to test against the actual
decoded instructions, and that makes me think that maybe yes, the
FunctionUnit should *not* be decoding the immediate, just pass it
through.

otherwise to achieve the same unit test coverage it would be necessary
to have the immediate decoding in the unit test.

i will go ahead and modify the compalu_multi.py to remove immediate
decoding/selection from here:

https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/experiment/compalu_multi.py;h=f9cb83ea13184bb6ff9ceedb7627b7ea67295c55;hb=HEAD#l166


----


here, it receives data in ALUInputData format (which is correct)

class ALUInputStage(PipeModBase):
    def __init__(self, pspec):
        super().__init__(pspec, "input")

    def ispec(self):
        return ALUInputData(self.pspec)

    def ospec(self):
        return ALUInputData(self.pspec)


however the output spec is a *modified* copy of the same data structure.

with "carry_in" being *generated* by ALUInputStage, ALUInputData should
*not* have "carry_in" as a field.

the reason is because it will never be set by the *user* of this stage,
and consequently a dangling wire will end up being created.

i've created a class ALUFirstInputData (bad name i know) which should
be used instead.  


-----

what's "so" intended for?

-- 
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 08may2020
From: Luke Kenneth Casson Leighton @ 2020-05-08 23:09 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5CYaj-4hPfbbTe6eoO49hj6VAwJqd3OrzMY-sFz4jO+w@mail.gmail.com>

On Fri, May 8, 2020 at 11:34 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> (Fixed the title, it's may not march.)

doh.  well spotted.

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

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