Angelo Salese
Angelo Salese
Updated OP message with easy to track base chipsets for x86 based systems.
Updated OP with the (mostly) i440bx additions from [PR#11037](https://github.com/mamedev/mame/pull/11037). As for the others: - queen.cpp can be converted to stub PCI driver (as per voyager.cpp), unless anybody wants to tackle...
- `konami/viper.cpp` should be easy now, given its limited PCI use beyond Voodoo itself. - `funworld/photoply.cpp` tracked by `sis85c496` in https://github.com/mamedev/mame/blob/master/src/mame/pc/pcipc_sis.cpp - `misc/savquest.cpp` tracked by `pciagp` in https://github.com/mamedev/mame/blob/master/src/mame/pc/pcipc.cpp
Edited OP with remaining blanks (in particular PPC chipset targets).
https://github.com/mamedev/mame/commit/6e1f17f676b772944049d5bfebda82bf51b228d4 takes care of `funworld/photoply.cpp`
What he said: either fix the conflicts or start over, 6 months (& 5 reviewers) for a XML change that should've split in at least 3 different PRs is far...
The alternative is just outright close this PR myself, what do you choose?
I moved it back because there are two outstanding issues there: 1. in order to rewrite the _Blitter_ there's a catch: the BIOS actively uses it asap to do some...
You didn't check one thing: 2/6 mode select is in TAB -> Machine Configuration  I feel like it shouldn't necessarily be there (it's a pad toggle...
I mean: that's not ideal either, my experience with a real PCE pad is that I quickly push back and forth the autofire lever because I know what's the state...