Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
H
HDL
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
RTSD
HDL
Commits
e0271902
Commit
e0271902
authored
Nov 24, 2014
by
Eric Kooistra
Browse files
Options
Downloads
Patches
Plain Diff
More on zip files and RadioHDL view points.
parent
33199e76
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
tools/hdltool_readme.txt
+11
-3
11 additions, 3 deletions
tools/hdltool_readme.txt
with
11 additions
and
3 deletions
tools/hdltool_readme.txt
+
11
−
3
View file @
e0271902
...
@@ -525,10 +525,18 @@ g) regression test script
...
@@ -525,10 +525,18 @@ g) regression test script
101) More ideas
101) More ideas
a) zip script
a) zip scripts
- zip all required libraries for a certain level library --> useful for somebody who wants to reuse a library.
A zip script can gather all sources that are needed for a particular RadioHDL view point, eg.
- zip all required libraries for a certain level library --> useful for somebody who wants to reuse a HDL library.
- zip all code necessary to run Python test cases on HW target --> useful for somebody who only wants to use the HW.
- zip all tool environent code --> useful for somebody who wants to use our tool flow but not our HDL.
- zip all tool environent code --> useful for somebody who wants to use our tool flow but not our HDL.
Related to this is (how) can we more clearly divide up the RadioHDL/ directory to eg. reuse only parts of it and
to develop these in other locations/repositories (eg. GIT). Eg. the applications/ directory may not be needed or
even suitable in RadioHDL/ because applications could be kept elsewhere, even in another repository at another
institute.
b) support dynamic generation of IP
b) support dynamic generation of IP
Very preliminary ideas:
Very preliminary ideas:
Currently the MegaWizard or QSYS component description file is fixed and created manually in advance via the
Currently the MegaWizard or QSYS component description file is fixed and created manually in advance via the
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment