Conversation
|
I think we need to drop the scastie support for now? |
|
Scastie is one of the most useful links on this page. Keeping around a link to a scastie for a prior chisel version would be great. |
I think the readme doesn't need backport. scastie cannot invoke firtool is the main issue. I think we need a RPC compiler API for scasite. |
jackkoenig
force-pushed
the
chisel5-readme
branch
from
91269d4 to
62cef75
Compare
jackkoenig
force-pushed
the
chisel5-readme
branch
3 times, most recently
from
5854d7b to
49f34c7
Compare
Scastie is still useful for showing basic concepts, you don't always need Verilog for that. It's a shame we can't run it with firtool but I still intend to keep it around (and just generate FIRRTL)
Agreed, I having both a 5.0.0 and a 3.6 version on here and I think we should keep it that way for a while
I'm not going to backport, but keeping the main README with a couple of versions of Chisel Scasties is useful
That is a large undertaking that involves funding for compute and a lot of sysadmin work that I don't think anyone really wants to do. It may be possible to get the Scastie devs to allow alternative Docker containers in which case maybe we can get one that has firtool installed. Alternatively, maybe we could do something with Compiler Explorer. |
| - [What does Chisel code look like?](#what-does-chisel-code-look-like) | ||
| - [LED blink](#led-blink) | ||
| - [FIR Filter](#fir-filter) | ||
| - [Getting Started](#getting-started) | ||
| - [Bootcamp Interactive Tutorial](#bootcamp-interactive-tutorial) | ||
| - [A Textbook on Chisel](#a-textbook-on-chisel) | ||
| - [Build Your Own Chisel Projects](#build-your-own-chisel-projects) | ||
| - [Guide For New Contributors](#guide-for-new-contributors) | ||
| - [Design Verification](#design-verification) | ||
| - [Documentation](#documentation) | ||
| - [Useful Resources](#useful-resources) | ||
| - [Chisel Dev Meeting](#chisel-dev-meeting) | ||
| - [Data Types Overview](#data-types-overview) | ||
| - [Contributor Documentation](#contributor-documentation) | ||
| - [Useful Resources for Contributors](#useful-resources-for-contributors) | ||
| - [Compiling and Testing Chisel](#compiling-and-testing-chisel) | ||
| - [Running Projects Against Local Chisel](#running-projects-against-local-chisel) | ||
| - [Chisel3 Architecture Overview](#chisel3-architecture-overview) | ||
| - [Chisel Sub-Projects](#chisel-sub-projects) | ||
| - [Which version should I use?](#which-version-should-i-use) | ||
| - [Roadmap](#roadmap) |
There was a problem hiding this comment.
VSCode auto regenerated this which is both annoying for the churn but nice for the guaranteed accuracy.
jackkoenig
force-pushed
the
chisel5-readme
branch
2 times, most recently
from
3c631b6 to
ca017e2
Compare
| Chisel consists of 4 Scala projects; each is its own separate compilation unit: | ||
|
|
||
| * [`core`](core) is the bulk of the source code of Chisel, depends on `macros` | ||
| Chisel consists of several Scala projects; each is its own separate compilation unit: |
There was a problem hiding this comment.
Nit: why are we putting these arguably less interesting things first in the list? Should we go in at least alphabetical order?
There was a problem hiding this comment.
It's contributor documentation so it's helpful to know where code is. Alphabetical order makes sense although things that come first in the alphabet depend on things that come later.
jackkoenig
force-pushed
the
chisel5-readme
branch
from
ca017e2 to
397e522
Compare
4 participants
Contributor Checklist
docs/src?Type of Improvement
API Impact
No impact
Backend Code Generation Impact
No impact
Desired Merge Strategy
Release Notes
Reviewer Checklist (only modified by reviewer)
3.5.xor3.6.xdepending on impact, API modification or big change:5.0.0)?Enable auto-merge (squash), clean up the commit message, and label withPlease Merge.Create a merge commit.