Implement support for bitwise ROM dumps

[munt]

Implement support for bitwise ROM dumps

[sergm]

@sergm , wanted to confirm that your bitwise ROM handling routines are working perfectly. In DOSBox Staging branch https://github.com/dosbox-staging/dosbox-staging/tree/kc/versioned-mt32-1, I've tested MT-32 1.04 through Blue Ridge, and CM-32L 1.00 and 1.02 using the identifyROMFile and mergeAndAddROMFiles functions, including played games with them.

From Staging's perspective, we're all set for 2.5.0!

Great news, I'll bump version 2.5.0 then.

The only version I haven't tested is MT-32 2.04 because it's not part of the MAME MT-32 or CL-32L sets.
Have you been able to find it?

Yes, I've also confirmed the validity of my ROM dump with @dwhinham (our dumps matched), so I'm pretty sure about it. Note, however, the control ROM IC of the new-gen unit isn't split (which can be seen in the service notes v.3).

[sergm]

You welcome :)
If you encounter an oddness in the new API, please let me know before I close the issues and tag a new lib version.

[kcgen]

Thanks for supporting the original bitwise ROM dump format, @sergm!
We will use your new functionality to let users configure a specific model and version to load, assuming they have a pool of uniquely named ROMs.
Regards.

[kcgen]

If you encounter an oddness in the new API, please let me know before I close the issues and tag a new lib version.

@sergm , wanted to confirm that your bitwise ROM handling routines are working perfectly. In DOSBox Staging branch https://github.com/dosbox-staging/dosbox-staging/tree/kc/versioned-mt32-1, I've tested MT-32 1.04 through Blue Ridge, and CM-32L 1.00 and 1.02 using the identifyROMFile and mergeAndAddROMFiles functions, including played games with them.

From Staging's perspective, we're all set for 2.5.0!

[kcgen]

The only version I haven't tested is MT-32 2.04 because it's not part of the MAME MT-32 or CL-32L sets.
Have you been able to find it?

[kcgen]

Thank you @sergm!