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 29 commits intogatecat:masterfrom
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.
there was a degree of caution not to pick a tile too close to the edge of the device because that could falsely cause some extra edge routing to be included, have you checked this?
| "PIOA.SEIO18.BASE_TYPE" => vec![Bel::make_seio18(0)], | ||
| "PIOB.SEIO18.BASE_TYPE" => vec![Bel::make_seio18(1)], | ||
| "PIOA.DIFFIO18.BASE_TYPE" => vec![Bel::make_diffio18()], | ||
| "PIOB.DIFFIO18.BASE_TYPE" => vec![Bel::make_diffio18()], |
There was a problem hiding this comment.
I don't think PIOB.DIFFIO18 should ever happen?
There was a problem hiding this comment.
I don't think so either, will remove
| 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?
util/fuzz/primitives.py
Outdated
There was a problem hiding this comment.
I think we shouldn't scrape descriptions from the lattice html unfortunately. It creates a theoretical copyright issue (as this is text rather than just a raw fact about an FPGA) particularly when they often reference weird lattice internal things, even if they're public facing docs.
There was a problem hiding this comment.
I've removed the ones from the primitives.py file, but made it so definitions that get scraped in from the web docs have the lattice descriptions. Not sure if this is good enough or not; easy enough to keep them out altogether if needed though
…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. |
2 participants
The changes here are related to: