Ultrasound (GUS) library development
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- operating-systems
Research direction
The issue names no files, tests or entry points; it lists open research questions about Gravis Ultrasound hardware (RAM, DMA, voices, UltraMAX, NMI signalling, IRQ enable bits). Start by reading the existing Sound Blaster library in the repository, which the author says is the model for this work. Done would mean the maintainer agrees on a concrete scope and a first deliverable, which the thread does not yet define.
Written by the indexing model from the issue text.
Description
I've developed the Sound Blaster library into quite a useful library, now it's the Gravis Ultrasound's turn. There's a lot to play with, considering the onboard RAM, DMA, on/off bits, 14 to 32 voices, and lots of undocumented hardware quirks and I/O ports. Perhaps we can figure out the UltraMAX part as well. Perhaps we can figure out the part that SBOS uses to signal NMI when Sound Blaster I/O ports are involved. Perhaps we can figure out whether or not those IRQ enable bits matter.
- Dominant language
- C
- Stars
- 243
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 joncampbell123/doslib
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
joncampbell123/doslib#71 ·
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
joncampbell123/doslib#69 · 1 comment ·
-
Difficulty 4/5 Over a week Newbie friendliness 12/100
joncampbell123/doslib#64 ·
-
Difficulty 3/5 Half a day Newbie friendliness 25/100
joncampbell123/doslib#62 · 3 comments ·
-
Difficulty 2/5 Under an hour Newbie friendliness 35/100
joncampbell123/doslib#61 ·
All issues in joncampbell123/doslib
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
FujiNetWIFI/fujinet-lib#186 ·
Maintainers usually reply within 1 day
-
VIEW_TYPE set for computer playersPossibly taken @Loobinex claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 Under an hour Newbie friendliness 78/100
brunodev85/winlator-app#90 ·