-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doc for adding a new part to PrjXray. #1486
Conversation
NEWPART.md
Outdated
@@ -0,0 +1,203 @@ | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be in docs/
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, makes sense. The question is, /only/ in docs as .rst, or also have an .md version? I noticed that the getting started readme exists in both formats.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll ask for re-reviews after updating the content here, and then when it looks good, I'll convert it to an .rst file under docs/.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mkurc-ant , @litghost , the new doc (docs/newpart.rst) is on readthedocs, ready for review. Ignore the NEWPART.md file; I'll delete it before merging. Start here: https://symbiflow--1486.org.readthedocs.build/projects/prjxray/en/1486/db_dev_process/index.html (to see where I've put the new page in the hierarchy), then click on "Guide to adding...".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it time to delete this file?
NEWPART.md
Outdated
|
||
* Rerun the top make command, `make -j32 MAX_VIVADO_PROCESS=32 db-part-only-artix7_100t` | ||
|
||
### Step 5 ### |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, good catch. I'll leave this comment unresolved, and add a comment to those PRs when this doc's final location is determined.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also need to check if f4pga/f4pga-arch-defs#1791 affects my instructions (under "Database Updates")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You have written this doc more like a report of what you did and how. In my opinion an instruction should be written in a more impersonal way.
NEWPART.md
Outdated
Clone your fork (replace "tcal-x" with your GitHub ID): | ||
|
||
``` | ||
git clone git@github.com:tcal-x/prjxray.git |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You may just point to the SymbiFlow/prjxray. There will be no need for instructing a user to replace your github id.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've replaced "tcal-x" with "", since I don't want them to start hacking directly on their clone of SymbiFlow's repo. Yes, if they know enough git they will know how to update things so they can commit to their own fork later, but it seems simpler if they start with their own fork...
4aa481f
to
9698861
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks great! Let's cleanup the handful of comments, and get this merged!
Signed-off-by: Tim Callahan <tcal@google.com>
Signed-off-by: Tim Callahan <tcal@google.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Tim Callahan <tcal@google.com>
Signed-off-by: Tim Callahan <tcal@google.com>
Signed-off-by: Tim Callahan tcal@google.com