|
Re: Submitting driver to github?
04/12/19 03:44 AM
|
|
|
Have you looked at any of the modern skeleton drivers, like the glass TTYs that AJR keeps adding? They don't do much more than document ROMs and allow you to view the disassembly in the debugger. Documentation goes in comments. Once again, there are plenty of examples in drivers that do nothing.
Here's an example of a driver that does nothing besides document the ROMs and hardware, and allow you to view the video and printer graphics ROM contents (even the CPU RAM/ROM mapping is not understood): https://github.com/mamedev/mame/blob/master/src/mame/drivers/anzterm.cpp
We do need the ROMs, and there are a variety of ways to make sure we get them.
What do you mean by a "previously unknown set"? A different program running on a supported system, or a completely new system? In either case, you add a machine definition and open a pull request, and supply us with ROMs and any other supporting materials so that anyone interesting in working on it in the future has as much to work with as possible.
|
|