WIP: Merges for documentation and to support LIFCL 33/33U#49
WIP: Merges for documentation and to support LIFCL 33/33U#49jdavidberger wants to merge 35 commits intogatecat:mainfrom
Conversation
- Added support for related BELs - Added support to parse compressed bitstreams - Support new device attributes - Support serializing deltas for checkpoint / debugging
…tas; refactor logic for tiletypes which configure adjacent tiles
jdavidberger
changed the title
| This serves as a master listing of each device and metadata associated with that device: | ||
|
|
||
| - packages: Comes from various lattice documentation, can also be seen by looking at the radiant device selection dialog. | ||
| - frame metadata: There are various necessary peices of data here. All are available in the "sysCONFIG Guide for Nexus Platform" document from the lattice website. |
There was a problem hiding this comment.
might be nice to expand this a bit more?
There was a problem hiding this comment.
I'm going to push the db changes for overlays and once that is all sorted and looks good, do a doc pass on these things
| if in_metadata && self.check_preamble(&COMMENT_END) { | ||
| if curr_meta.len() > 0 { | ||
| self.metadata.push(curr_meta.to_string()); | ||
| if curr_meta.is_ascii() { |
There was a problem hiding this comment.
looks like spaces and tabs got mixed here?
…t of introspective features using the full node db
… to different api calls
…for merge/commit into db
|
I increased the scope by a decent margin; I added overlays and a general purpose pip solver. Probably the big thing now is making sure the overlays / 000 fuzzer make sense and are documented well enough. |
gatecat
left a comment
gatecat
left a comment
There was a problem hiding this comment.
in general looking good, had another glance at this with a few more comments. let me know if anything else is waiting on me!
docs/database.md
Outdated
|
|
||
| ### iptypes | ||
|
|
||
| These files are generated by various fuzzers associated with the given primitive. They map out the relationship between configuration parameters and the bits set in the bitstream. |
There was a problem hiding this comment.
maybe add a note that these specifically relate to configuration in the "IP space" (baseaddrs.json) rather than the main CRAM grid?
| lambda x: dict(arcs_attr=arcs_attr) if x == "YES" else {}, False) | ||
| lambda x: dict(arcs_attr=arcs_attr) if x == "YES" else {}, False, executor=executor) | ||
|
|
||
| # CIBMUXIN -> CIBMUXOUT |
There was a problem hiding this comment.
was there a specific reason for removing this?
There was a problem hiding this comment.
These get found in build-pip-overlays now
|
Sorry for the haitus, I had a work project kick into high gear. I think it is fairly close to being mergeable soon, but will require some discussion about the approach probably |
2 participants
The changes here are related to: