If you run -listdevices on kingofb and ringking in 0.191 and examine the output closely, you'll see kingofb has the nmigate device configured as "Input Merger (all high)," but ringking has it instead as "Input Merger (any high)." This discrepancy, which I've just fixed in GIT, is why the latter wasn't working: it disabled the vblank interrupt shared by three of the four CPUs when it was supposed to be enabled by the main CPU writing a 1 to it.
|
Index 
Flat 
Re: Ring King not working?
Reply
Re: Ring King not working?
