Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-04-29 21:42 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 #29 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
jacob on looking at minerva they did something which i think would be really
useful to copy.

they created "cacheless" memory classes and "cached" versions conforming to the
same interface.

this allows an incremental approach where testing of one component is not
critically dependent on another that hasn't been written yet.

-- 
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 257] Implement demo Load/Store queueing algorithm
From: bugzilla-daemon @ 2020-04-29 21:39 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-257-13@https.bugs.libre-soc.org/>

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

--- Comment #29 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
if you can record some brief notes, after the oct 2020 deadline, or if we have
less time pressure, it will be good to come back to this.

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

^ permalink raw reply

* Re: [libre-riscv-dev] memory interface diagram woes
From: Luke Kenneth Casson Leighton @ 2020-04-29 15:10 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxr-xS_1WHa4U=-MkErRCdX_BCY4Rgvh+2XH8msmwmyJg@mail.gmail.com>

oh god!  POWER LD/ST has an indexed version and an immediate version
of instructions!  so that's *eight* possible variants:

* LD/ST
* Update y/n
* Immediate/Indexed

fortunately i have the logic for an immediate-or-OP2 already drawn out.

this is getting ridiculous! :)

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-04-29 11:16 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
Bug 216 depends on bug 257, which changed state.

Bug 257 Summary: Implement demo Load/Store queueing algorithm
https://bugs.libre-soc.org/show_bug.cgi?id=257

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

-- 
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 257] Implement demo Load/Store queueing algorithm
From: bugzilla-daemon @ 2020-04-29 11:16 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-257-13@https.bugs.libre-soc.org/>

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

Jacob Lifshay <programmerjake@gmail.com> changed:

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

--- Comment #28 from Jacob Lifshay <programmerjake@gmail.com> ---
since i'm effectively stalled on the algorithm I've been working on (it should
work, just not good at writing it out properly) and the one luke's been working
on should work well enough (bug 216, I think), will be switching to just
implementing that one.

If there's more time later, I can try again and reopen this bug.

-- 
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 132] SIMD-like nmigen signal for partitioning
From: bugzilla-daemon @ 2020-04-29  8:59 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-132-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=132
Bug 132 depends on bug 171, which changed state.

Bug 171 Summary: partitioned comparison operators
https://bugs.libre-soc.org/show_bug.cgi?id=171

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

-- 
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 171] partitioned comparison operators
From: bugzilla-daemon @ 2020-04-29  8:59 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-171-13@https.bugs.libre-soc.org/>

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

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

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

-- 
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 196] Formal correctness proof needed for the IEEE754 FPU
From: bugzilla-daemon @ 2020-04-29  8:56 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-196-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=196
Bug 196 depends on bug 162, which changed state.

Bug 162 Summary: Formally Verify the FSGNJ module
https://bugs.libre-soc.org/show_bug.cgi?id=162

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

-- 
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 162] Formally Verify the FSGNJ module
From: bugzilla-daemon @ 2020-04-29  8:56 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-162-13@https.bugs.libre-soc.org/>

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

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

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

-- 
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 294] New: usage statistics needed for POWER9 architecture
From: bugzilla-daemon @ 2020-04-29  8:55 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 294
           Summary: usage statistics needed for POWER9 architecture
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Source Code
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

we need to specifically target the register file port allocation and
the bus multiplexing to meet the performance requirements.  we cannot
go all-out because the power consumption and wiring would be far too
high.

see https://groups.google.com/d/msg/comp.arch/qeMsE7UxvlI/HjCDBp5yBgAJ

-- 
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] HTTaP and Design for Test (was Re:  circuitjs)
From: whygee @ 2020-04-28 19:37 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDw=eAbYj55NOayUVn_NzLX8v0ohvBatnQd-SVaL1RV=mQ@mail.gmail.com>

On 2020-04-28 17:35, Luke Kenneth Casson Leighton wrote:
> the actual
> server-side implementation of a JSONRPC server was done in a mere *50*
> lines of code.  25 of those lines involved exception/error handling!
> other JSONRPC servers that i've seen are thousands of lines of
> completely unnecessary code.

speaking of which : did I mention I rebooted the design of my HTTaP 
server ?

http://httap.org : It's a protocol for TAP over (hidden in) HTTP.

It's currently live on http://httap.org:60075 if you want to see
(the port number may change and it's not running 24/7)

The total number of lines in C is 1203 for now and I have not yet
added much support for user-provided functions but don't laugh yet.
it's convoluted but really required !

It was initially designed about 8 years ago to run INSIDE GHDL and
control/report VHDL simulations. For example you provide your own user
"words" to control the state of input and output signals then "plug" the
commands to actual VHDL code. Then write the testbenches in JS
or whatever, co-simulate with FPGA or compare between different
models...

My recent designs include a TAP (Test Access Port) that exactly
mimics the real pins that would be provided on the outside of the
FPGA or ASIC, it could be JTAG or anything convenient. I use a
half-duplex SPI-like interface to send and receive control/status
data, inject and exfiltrate given signals from a design...

The HTTaP interface is very friendly to microcontrollers and Raspberry 
Pis,
which is an obvious choice for this kind of application.

The protocol/interface looks the same to the JS GUI, just change the 
backend.
Thus, the emulation, the simulation, the FPGA and the ASIC look
exactly the same. That's "design for test".

It's even a great idea to start the design (and assembly of all the 
modules)
from the TAP interface itself, building from there and expanding.
This makes sure ALL circuits can be thoroughly tested and accessed,
little by little while the circuit is built, not at the last moment,
which is a great insurance of having your chips tested and running
very fast after delivery from the fab.

I hope this sparks some more ideas and boosts Libre-SOC :-)

> 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] circuitjs
From: whygee @ 2020-04-28 19:10 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5mBJff_+56LFAANFL0hdHtZ_T--1BvjeTq2YxQKSsk_A@mail.gmail.com>

On 2020-04-28 16:53, Jacob Lifshay wrote:
>> https://github.com/sharpie7/circuitjs1/commit/323f530ce4c409316e2bab8277636deced3070fc
wait, YOU did it ? :-O
awesome !
For now I play with :
incremeters http://tinyurl.com/y7mseqfd
Carry-lookahead adders
complete ALU datapath http://tinyurl.com/rhonlsz
latches http://tinyurl.com/y8jjxd2x
shift registers, sequencers and so on,
very low-level but absolutely indispensable...
circuitjs has many quirks and bugs but
the qualities are not matched yet.

>> being able to have *interactive*
>> subsets of the circuits we're deploying would be absolutely fantastic.
that's all the point of a recently published article I wrote about it.
Can Jacob tell the developers about it ? :-)

> If we were to try to run much more than some really simple circuits, it
> would need things like multi-bit buses and a much faster simulator and
> subcircuits (though I think it may already have subcircuits).
I have not run into hard limitations so far, except screen size :-D

> BTW, the offline Java version is quite a bit faster than the online 
> version
> which is made using a Java to Javascript translator (GWT).
for now speed is not the point for me :
on hackaday.io we use circuitjs a LOT to discuss circuit topologies,
ping and pong ideas at each other, demonstrate stuff...

the circuitjs system allows sharing with much fewer limits than "normal 
programs"
and can be embedded in tutorials and educational webpage. A bit of JS 
could
detect a click to swap an <img> into an <iframe> that simulate the 
principle.

For number theory I have used JS-animated SVG but it's so painful and 
long to write,
but Luke could "build" the scoreboard before our eyes in a long HTML 
page,
showing each sub-element one by one and assembling them, then show their 
combined
behaviours...

The scheduler has long reached a state where even Luke has difficulties 
managing
its subtleties so that method would not only help him, but more 
importantly OTHERS
so they can take over his work when needed. So far, I don't feel I could 
ever,
despite my little understanding of the CDC6600.

>> i'm even tempted to suggest putting in a new NLNet Grant request to 
>> cover it.
> Maybe write a BLIF to CircuitJS translator :)
> allows us to export from yosys to circuitjs
I've been considering finding ways to convert from/to circuitjs
to/from VHDL... that would be a killer.
At least a "filter" to transform the .txt outputs, recognize
the basic gates and map them to those of my library (or sxlib)
and/or vice versa.

> Jacob
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] memory interface diagram woes
From: Luke Kenneth Casson Leighton @ 2020-04-28 16:30 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzavTqZ-_cw7BtHNHwnAHXjJX=xC29cX9cY4cRWTnerUQ@mail.gmail.com>

aw god this isn't funny any more! (actually... it is).  there's a
store-with-update that's separate from load-with-update.  so there are
*four* combinations:

* LD Mode will activate Issue, GoRead1, GoAddr then GoWrite1
* LD-UPDATE Mode will *additionally* activate GoWrite2.
* ST Mode will activate Issue, GoRead1, GoRead2, GoAddr then GoStore.
  ST-UPDATE Mode will *additionally* activate GoWrite2.

i might be able to recover the current diagram without rewriting it.

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] circuitjs
From: Luke Kenneth Casson Leighton @ 2020-04-28 15:35 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6niqhbnv6Oe2ZTdUbxAiQ82FWX=h+QAEfvAm2JpR=rkg@mail.gmail.com>

On Tue, Apr 28, 2020 at 4:11 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> I heard that most of google's web frontends (like gmail) are written using
> GWT (or something similar).

and it makes for an incredible effectiveness as a result.  the team
only need write code *once* and it can run on desktop *and* as a
mobile app, but not only that, the subdivision into (close to)
Model-View-Controller by inherent design means that actual front-end
GUI code is pretty much completely separate from "stuff that does
stuff".

using pyjs a client commented on how sparse (how little) code was.
and it was because everything that was "active" - handling data - was
done using a JSON RPC client-server architecture.  the actual
server-side implementation of a JSONRPC server was done in a mere *50*
lines of code.  25 of those lines involved exception/error handling!
other JSONRPC servers that i've seen are thousands of lines of
completely unnecessary code.

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] memory interface diagram woes
From: Luke Kenneth Casson Leighton @ 2020-04-28 15:28 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDw4Hdq5JHQxtkcXzY8h7A=m2yUvcBOkjoTpC8uKRgnojA@mail.gmail.com>

https://libre-soc.org/3d_gpu/ld_st_comp_unit.jpg

okaaaaay, finally.  (btw don't tell no-one i watch American Ninja
Warrior re-runs whilst drawing these).

there's three modes:

* LD mode - OP1 READ, OP2 WRITE, memory read
* LD-UPDATE mode - OP1 READ *and* WRITE, OP2 WRITE
* ST mode - OP1 READ, OP2 READ, memory write

notes:

* ALU and ADR latch covers the case where the Adder only triggers
"result ok" for 1 cycle, latching the output EA (effective address)
indefinitely, where ALU-SR's job is to signal that the address is
ready.  the two separate latches are because you musn't de-latch the
address from the LD/ST-Port just because GoAddr acknowledgement
occurred

* likewise LD-sr latches on "LD_OK" and captures the LD Data output
from the LD/ST-Port, where the WR-sr latch reacts differently.  i am
not entirely certain that two separate latches are needed here, to be
honest, however i believe it is "safe" to have them separate.

* SHADOW_N stops all write activity until it is *definitely* known
that the possibility for exceptions has passed.  this is *the* reason
why we can do a full O-o-O design with "precise exceptions": something
that the "Academic" literature does *NOT* recognise as being possible
with a 6600-style architecture.

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] circuitjs
From: Jacob Lifshay @ 2020-04-28 15:10 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDy1boM22KUP3_L5M+KCNO8q9fy2+t8Pkgqc+EWCQwrKHQ@mail.gmail.com>

On Tue, Apr 28, 2020, 08:04 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

>
> GWT.  *scream*!  i remember GWT - i was the lead developer of the
> python-to-javascript language translator, pyjs.  ha, that's amazing
> that people still use GWT.
>

I heard that most of google's web frontends (like gmail) are written using
GWT (or something similar).

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] circuitjs
From: Luke Kenneth Casson Leighton @ 2020-04-28 15:03 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5mBJff_+56LFAANFL0hdHtZ_T--1BvjeTq2YxQKSsk_A@mail.gmail.com>

On Tue, Apr 28, 2020 at 3:54 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> If we were to try to run much more than some really simple circuits, it
> would need things like multi-bit buses and a much faster simulator and
> subcircuits (though I think it may already have subcircuits).

yes, looks like it.

> BTW, the offline Java version is quite a bit faster than the online version
> which is made using a Java to Javascript translator (GWT).

which is good to have in mirroring scratch having an online and offline version.

GWT.  *scream*!  i remember GWT - i was the lead developer of the
python-to-javascript language translator, pyjs.  ha, that's amazing
that people still use GWT.

> Maybe write a BLIF to CircuitJS translator :)
> allows us to export from yosys to circuitjs

that would save an awful lot of time.

l.

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

^ permalink raw reply

* [libre-riscv-dev] [Bug 293] evaluate an online circuit-editor (with simulator preferably)
From: bugzilla-daemon @ 2020-04-28 14:56 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-293-13@https.bugs.libre-soc.org/>

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

Jacob Lifshay <programmerjake@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |programmerjake@gmail.com

--- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
maybe add yosys to circuitjs translator:

http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-April/006163.html

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

^ permalink raw reply

* [libre-riscv-dev] circuitjs
From: Jacob Lifshay @ 2020-04-28 14:53 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDw4Hdq5JHQxtkcXzY8h7A=m2yUvcBOkjoTpC8uKRgnojA@mail.gmail.com>

On Tue, Apr 28, 2020, 07:44 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Tue, Apr 28, 2020 at 3:38 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > > oooo i looove it.
> > > https://github.com/sharpie7/circuitjs1
> >
> > Didn't occur to me to use it -- even though I created the QAM-256
> > Modulator/Demodulator example:
> >
> https://github.com/sharpie7/circuitjs1/commit/323f530ce4c409316e2bab8277636deced3070fc
>
> ooo, wooow, shiny :)
>
> although i am currently spaced-out at how sparkly and shiy circuitjs
> is (just ran the adder circuit example) i'm also really liking it from
> the "educational" perspective.  being able to have *interactive*
> subsets of the circuits we're deploying would be absolutely fantastic.
>

If we were to try to run much more than some really simple circuits, it
would need things like multi-bit buses and a much faster simulator and
subcircuits (though I think it may already have subcircuits).

Try and see how fast the QAM-256 example is, since that's a more
complicated circuit.

BTW, the offline Java version is quite a bit faster than the online version
which is made using a Java to Javascript translator (GWT).

>
> i'm even tempted to suggest putting in a new NLNet Grant request to cover
> it.
>

Maybe write a BLIF to CircuitJS translator :)
allows us to export from yosys to circuitjs

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] memory interface diagram woes
From: Luke Kenneth Casson Leighton @ 2020-04-28 14:43 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4VuWoWsYR7N4nXUcoeFadsBSht5zSS0pZhds+x=zuP6Q@mail.gmail.com>

On Tue, Apr 28, 2020 at 3:38 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> > oooo i looove it.
> > https://github.com/sharpie7/circuitjs1
>
> Didn't occur to me to use it -- even though I created the QAM-256
> Modulator/Demodulator example:
> https://github.com/sharpie7/circuitjs1/commit/323f530ce4c409316e2bab8277636deced3070fc

ooo, wooow, shiny :)

although i am currently spaced-out at how sparkly and shiy circuitjs
is (just ran the adder circuit example) i'm also really liking it from
the "educational" perspective.  being able to have *interactive*
subsets of the circuits we're deploying would be absolutely fantastic.

i'm even tempted to suggest putting in a new NLNet Grant request to cover it.

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] memory interface diagram woes
From: Jacob Lifshay @ 2020-04-28 14:38 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwaLg3UCF_P+KLDRmUpfYFZf==AKKrevE+g24ytpWiYDw@mail.gmail.com>

On Tue, Apr 28, 2020, 07:27 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Tue, Apr 28, 2020 at 2:33 PM <whygee@f-cpu.org> wrote:
> > have a look at http://www.falstad.com/circuit/circuitjs.html
> > it has some digital simulation capabilities, and lets you
> > exchange the designs with simple minified links.
>
> oooo i looove it.
> https://github.com/sharpie7/circuitjs1


Didn't occur to me to use it -- even though I created the QAM-256
Modulator/Demodulator example:
https://github.com/sharpie7/circuitjs1/commit/323f530ce4c409316e2bab8277636deced3070fc

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

* [libre-riscv-dev] [Bug 293] New: evaluate an online circuit-editor (with simulator preferably)
From: bugzilla-daemon @ 2020-04-28 14:27 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 293
           Summary: evaluate an online circuit-editor (with simulator
                    preferably)
           Product: Libre-RISC-V Website
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: website
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

https://github.com/sharpie7/circuitjs1
https://github.com/circuitdiagram/circuitdiagram

a lot of diagrams are being hand-drawn, it would be extremely useful
to illustrate them online and have them actually run in a simulator

-- 
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] memory interface diagram woes
From: Luke Kenneth Casson Leighton @ 2020-04-28 14:26 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <365bd897eff6a78ed70f9c07a60c8c4e@f-cpu.org>

On Tue, Apr 28, 2020 at 2:33 PM <whygee@f-cpu.org> wrote:
>
> On 2020-04-28 13:56, Luke Kenneth Casson Leighton wrote:
> > fail.  on to version *12*.  it's about 90 minutes to draw and verify
> > each diagram.
>
> have a look at http://www.falstad.com/circuit/circuitjs.html
> it has some digital simulation capabilities, and lets you
> exchange the designs with simple minified links.

oooo i looove it.
https://github.com/sharpie7/circuitjs1

another one, circuitdiagram
https://github.com/circuitdiagram/circuitdiagram


> Then you can integrate digital (sub-)circuits as IFRAMEs
> in webpages to explain and expose the principles of your design.
> It's not the very best system but it's incredibly useful
> and flexible. You won't use DIA anymore ;-)

that's a great idea.

_______________________________________________
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] memory interface diagram woes
From: whygee @ 2020-04-28 13:33 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwtjksKH3odd0gfeBbLhVVPm=KD3auoihJq4X+-ROOg6g@mail.gmail.com>

On 2020-04-28 13:56, Luke Kenneth Casson Leighton wrote:
> fail.  on to version *12*.  it's about 90 minutes to draw and verify
> each diagram.

have a look at http://www.falstad.com/circuit/circuitjs.html
it has some digital simulation capabilities, and lets you
exchange the designs with simple minified links.
Then you can integrate digital (sub-)circuits as IFRAMEs
in webpages to explain and expose the principles of your design.
It's not the very best system but it's incredibly useful
and flexible. You won't use DIA anymore ;-)

> 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

* [libre-riscv-dev] [Bug 196] Formal correctness proof needed for the IEEE754 FPU
From: bugzilla-daemon @ 2020-04-27 20:45 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-196-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=196
Bug 196 depends on bug 163, which changed state.

Bug 163 Summary: Formally Verify the FPMAX module
https://bugs.libre-soc.org/show_bug.cgi?id=163

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

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

^ permalink raw reply

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