Fine grained clock domains
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- tooling
Research direction
Begin by locating the linker implementation and its handling of kernel-level target frequencies. Define how identical frequencies are coalesced and how the linker reports and enforces an upper limit on clock domains; done means these behaviors are covered and user-facing messages are produced.
Written by the indexing model from the issue text.
Description
Enable the linker to create a clock domain for each kernel, by specifying target frequency at kernel level. Linker will attempt to coalesce clock domains of identical frequency to reduce complexity. Some reasonable upper limit on clock domains needs to be established and enforced by the linker via messages to the user
- Dominant language
- Tcl
- Stars
- 48
- Forks
- 23
- Avg merge
- 19h 53m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Xilinx/SLASH
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Supporting asynchronous HBM clock crossing and AXI width conversionPossibly taken @hpc-aulmamei claimed this 4 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
device bring up issue (v80-smi write-static-shell)Possibly taken @quetric claimed this 7 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
V80 SLASH shell silently drops host `s_axi_control` writes to offsets `0x40–0xBF`Possibly taken @quetric claimed this 10 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/gh-aw-workshop#4220 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenHands/extensions#738 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
bmad-code-org/BMAD-METHOD#3039 ·
Maintainers usually reply within 1 day
-
Link Checker ReportPossibly taken @keraron claimed this today. Openautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
a2aproject/A2A#2297 ·
Maintainers usually reply within 1 day