summaryrefslogtreecommitdiffstatshomepage
path: root/src/mame/drivers/playch10.cpp (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Rearrange source to match project structure (done using the script in ↵ Vas Crabb2022-06-271-1932/+0
| | | | src/tools).
* playch10.cpp: Replaced RP5H01 rom in prototype dumps. (#9386) 0kmg2022-03-261-6/+6
|
* playch10.cpp: Use memory banks for nametable RAM. (#9442) 0kmg2022-03-201-1/+4
| | | | | famibox.cpp: Use memory banks for nametable RAM. cham24.cpp: Use memory banks for nametable RAM. multigam.cpp: Add PPU address map and use memory banks for nametable RAM.
* vsnes.cpp: Fixed Gumshoe regression. (#9438) 0kmg2022-03-191-1/+1
|
* bus/nes_ctrl: Split zapper sensor off as a reusable device. (#9417) 0kmg2022-03-171-0/+2
|
* playch10.cpp: A few more cleanups. (#9352) 0kmg2022-03-041-79/+54
| | | | | | | - Nametable RAM is now 2K, except for the two games (Rad Racer II, Gauntlet) that have extra RAM on daughter boards. - Removed unnecessary overridden machine/video start code for PinBot. - Added an address map for the PPU. - Further simplified initialization code for games that have VRAM or special RP5H01 usage. - Lots of conversion to C++-style comments with a few corrections along the way.
* playch10.cpp: Various cleanups. (#9349) 0kmg2022-02-281-159/+149
| | | | | - Modernized PRG ROM banking. - Cleaned up cart daughter board initialization code. - Fixed daughter board RAM sizes for Baseball Star, Pinbot, and Punch-Out. Punch-Out's is NVRAM and it now saves properly.
* Various NES and friends cleanups. (#9312) 0kmg2022-02-211-1/+1
| | | | | | | * nes.h: Removed ancient unused defines and variables. * playch10.cpp: Removed unused shared pointer. * vsnes.cpp: Changed BaseBall in titles to Baseball. * bus/nes: Cleaned up various device_type comparisons and set some consts const. * sound/nes_defs.h: Fixed a DPCM table entry that was off by one.
* nes.cpp, playch10.cpp, vsnes.cpp: Made zapper less bad. (#9284) 0kmg2022-02-091-5/+5
| | | | | | | | - Limited light detection to scanlines recently drawn by CRT. - Lowered light detection threshold to better reflect how real zapper behaves; color doesn't need to be white. - Bugs fixed: * not detecting hits on certain white objects * misdetecting hits on objects far away from the pointer * not being able to track where zapper is pointed in demo/test software
* Fixed game titles for Golly! Ghost! 2 (MT08195) and Excitebike. (#9253) 0kmg2022-02-041-3/+3
|
* playch10.cpp: Correct NT mirroring for various games (MT 02646). (#9220) 0kmg2022-01-271-9/+9
| | | | | | * playch10.cpp: Correct NT mirroring for various games (MT 02646). - Mark Excite Bike and Ninja Gaiden 2 as imperfect graphics. * Mark Rad Racer 1 and 2 as imperfect graphics while we're at it.
* playch10.cpp: dumped an alternate BIOS [Phill @NES4Life] Ivan Vangelista2021-12-071-3/+5
|
* Purge #include "rendlay.h" where not necessary AJR2021-01-041-1/+0
|
* emumem: Simplify memory management. [O. Galibert] Olivier Galibert2020-11-021-58/+228
| | | | | | | | | | | | | | | | | | | | API impact: - install_ram/rom/writeonly now requires a non-null pointer. If you want automatically managed ram, add it to a memory map, not in machine_start - install_*_bank now requires a memory_bank *, not a string - one can create memory banks outside of memory maps with memory_bank_creator - one can create memory shares outside of memory maps with memory_share_creator Memory maps impact: - ram ranges with overlapping addresses are not shared anymore. Use .share() - ram ranges touching each other are not merged anymore. Stay in your range Extra note: - there is no need to create a bank just to dynamically map some memory/rom. Just use install_rom/ram/writeonly
* drivers starting with p and q: removed read* and write* macros (nw) Ivan Vangelista2020-06-131-4/+4
|
* playch10.cpp: Fixed Player 1 Labels to match function (nw) Scott Stone2020-04-091-2/+2
|
* playch10.cpp: Corrected BIOS PPU ROM loading. [brizzo] Vas Crabb2019-10-071-19/+20
|
* PORT_CUSTOM simplification (nw) AJR2019-09-141-1/+1
| | | | | | | | | | | | - Remove both arguments from CUSTOM_INPUT_MEMBER (adding template parameters as necessary) - Remove 'param' from PORT_CUSTOM_MEMBER and assume 'device' is DEVICE_SELF (use PORT_CUSTOM_DEVICE_MEMBER if it isn't) - Replace PORT_CUSTOM_MEMBER with PORT_READ_LINE_MEMBER where applicable Add implicit DEVICE_SELF variants of PORT_READ_LINE_DEVICE_MEMBER and PORT_WRITE_LINE_DEVICE_MEMBER (nw) Remove ioport_field argument from PORT_CROSSHAIR_MAPPER (nw) captflag, gmgalax: Separate driver classes from base (nw)
* playch10: Fix order and updates for both screens Enik Land2019-07-111-6/+6
|
* n2a03.cpp : Add device_mixer_interface instead hardcoded tags cam9002019-04-021-1/+1
| | | | nes.cpp, mmc5.cpp : Fix sound volume
* Start cleaning up palette configuration: Vas Crabb2018-12-291-1/+1
| | | | | | | | | | * Basically, initialisers go in the constructor arguments, and things for setting format go in set_format. * Initialisation patterns can be specified with an enum discriminator or with a FUNC and optionally a tag. * Formats can be specified with an enum discriminator or a size and function pointer. * You must always supply the number of entries when setting the format. * When initislising with a paletter initialisation member, you can specify the entries and indirecte entries together. * The palette_device now has a standard constructor, so use .set_entries if you are specifying entry count with no format/initialisation. * Also killed an overload on delegates that wasn't being useful.
* -bus/nes/jaleco, pt554, bus/nes_ctrl/ctrl, hori, joypad: Removed MCFG and ↵ mooglyguy2018-12-201-18/+19
| | | | | | | | | | | | | | | MACHINE_CONFIG macros. [Ryan Holtz] -sound/asc, lmc1992, nes_apu, samples, video/ppu2c0x, ppu2c0x_vt: Removed MCFG macros. [Ryan Holtz] -audio/astrof, carnival, cclimber, cinemat, depthch, invinco, pulsar, spacefb, targ, tranqgun, turbo, vicdual vicdual-97271p, zaxxon: Removed MACHINE_CONFIG macros. [Ryan Holtz] -drivers/8080bw, astinvad, atarist, blockade, cham24, circus, cosmic, equites, famibox, gottlieb, gotya, gridlee, homerun, m10, m14, m63, mcr, meadows, mmagic, multigam, mw8080bw, nes, nes_vt, ninjakd2, playch10, safarir, segag80v, starcrus, starfire, suna8, super80, tankbatt, tattack, thief, tmnt, tnzs, triplhnt, vsnes: Removed MACHINE_CONFIG macros. [Ryan Holtz] -machine/genpin, mm1kb: Removed MACHINE_CONFIG macros. [Ryan Holtz]
* Spelling corrections (nw) AJR2018-11-251-1/+1
|
* cpu/pps4 - machine/pxa255, r10696, r10788, ra17xx, rf5c296, roc10937, ↵ Ivan Vangelista2018-10-291-1/+1
| | | | rp5c01, rp5c15, rp5h01, rtc4543, rtc65271, rtc9701, s2636, s3520cf, s3c2400, s3c2410, s3c2440, sa1043, scnxx562: removed MCFG macros (nw)
* -nvram: Removed MCFG, nw mooglyguy2018-08-241-3/+4
|
* Fix MT06192 sjy965252018-07-221-1/+1
| | | Chip'n Dale: Rescue Rangers was released in June 8, 1990 in Japan and USA.
* Allow per-device internal layouts and remove some more MCFG_ macros. Vas Crabb2018-07-161-1/+1
| | | | | | | | | | | Input and screen tags are now resolved relative to a layout's owner device. Easy way to demonstrate is with: mame64 intlc440 -tty ie15 Previously you'd only get the IE15 terminal's layout and you'd be unable to use the INTELLEC 4/40 front panel. Now you'll get the choice of layouts from both the system and the terminal device in video options.
* devcb3 Vas Crabb2018-07-071-26/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are multiple issues with the current device callbacks: * They always dispatch through a pointer-to-member * Chained callbacks are a linked list so the branch unit can't predict the early * There's a runtime decision made on the left/right shift direction * There are runtime NULL checks on various objects * Binding a lambda isn't practical * Arbitrary transformations are not supported * When chaining callbacks it isn't clear what the MCFG_DEVCB_ modifiers apply to * It isn't possible to just append to a callback in derived configuration * The macros need a magic, hidden local called devcb * Moving code that uses the magic locals around is error-prone * Writing the MCFG_ macros to make a device usable is a pain * You can't discover applicable MCFG_ macros with intellisense * Macros are not scoped * Using an inappropriate macro isn't detected at compile time * Lots of other things This changeset overcomes the biggest obstacle to remving MCFG_ macros altogether. Essentially, to allow a devcb to be configured, call .bind() and expose the result (a bind target for the callback). Bind target methods starting with "set" repace the current callbacks; methods starting with "append" append to them. You can't reconfigure a callback after resolving it. There's no need to use a macro matching the handler signatures - use FUNC for everything. Current device is implied if no tag/finder is supplied (no need for explicit this). Lambdas are supported, and the memory space and offset are optional. These kinds of things work: * .read_cb().set([this] () { return something; }); * .read_cb().set([this] (offs_t offset) { return ~offset; }); * .write_cb().set([this] (offs_t offset, u8 data) { m_array[offset] = data; }); * .write_cb().set([this] (int state) { some_var = state; }); Arbitrary transforms are allowed, and they can modify offset/mask for example: * .read_cb().set(FUNC(my_state::handler)).transform([] (u8 data) { return bitswap<4>(data, 1, 3, 0, 2); }); * .read_cb().set(m_dev, FUNC(some_device::member)).transform([] (offs_t &offset, u8 data) { offset ^= 3; return data; }); It's possible to stack arbitrary transforms, at the cost of compile time (the whole transform stack gets inlined at compile time). Shifts count as an arbitrary transform, but mask/exor does not. Order of mask/shift/exor now matters. Modifications are applied in the specified order. These are NOT EQUIVALENT: * .read_cb().set(FUNC(my_state::handler)).mask(0x06).lshift(2); * .read_cb().set(FUNC(my_state::handler)).lshift(2).mask(0x06); The bit helper no longer reverses its behaviour for read callbacks, and I/O ports are no longer aware of the field mask. Binding a read callback to no-op is not supported - specify a constant. The GND and VCC aliases have been removed intentionally - they're TTL-centric, and were already being abused. Other quirks have been preserved, including write logger only logging when the data is non-zero (quite unhelpful in many of the cases where it's used). Legacy syntax is still supported for simple cases, but will be phased out. New devices should not have MCFG_ macros. I don't think I've missed any fundamental issues, but if I've broken something, let me know.
* as if millions of this pointers suddenly cried out in terror, and were ↵ Vas Crabb2018-06-081-8/+8
| | | | | | | suddenly silenced * streamline templates in addrmap.h * get rid of overloads on read/write member names - this will become even more important in the near future
* Move the +1 to the proper place in the ROM BIOS macros - that's been Vas Crabb2018-05-291-1/+1
| | | | | | | | | confusing people for far too long. Yes, this is a change in behaviour. Add a valdiation check for ROMs with BIOS flag set that are unselectable, fix the things it uncovers. (nw) Fix other random stuff.
* diexec: Interrupt API changes (nw) AJR2018-05-181-2/+2
| | | | | | - PULSE_LINE is no longer a value. Existing uses have been changed to pulse_input_line with attotime::zero as the second argument. - Formerly only INPUT_LINE_NMI and INPUT_LINE_RESET were allowed with PULSE_LINE. INPUT_LINE_NMI no longer receives special handling; instead, CPU devices must specify which of their input lines are edge-triggered and thus may be used with zero-width pulses by overriding the execute_input_edge_triggered predicate. INPUT_LINE_RESET is still special-cased, however. - execute_default_irq_vector now allows a different default vector to be specified for each input line. This added flexibility may or may not prove useful.
* Revert "- Removed MACHINE/SOUND/VIDEO _START/_RESET macros. This has the ↵ Vas Crabb2018-05-161-2/+2
| | | | | | | | | | | | side effect of making machine-config overrides of these much" This reverts commit c83e2a853d4e1643fcc85b68ada3c6f7f33adea4. Revert "fix compile. (nw)" This reverts commit a259ba3e366f442a22a9341755ff58163869860c. GCC is being bad and allowing invalid C++ that other compilers reject.
* - Removed MACHINE/SOUND/VIDEO _START/_RESET macros. This has the side effect ↵ MooglyGuy2018-05-161-2/+2
| | | | | | of making machine-config overrides of these much uglier, but this is intended to discourage ongoing use, and will be gradually eliminated.
* More cleanup/streamlining of machine configuration and macros: Vas Crabb2018-05-151-2/+2
| | | | | | | | | | | | | * Get rid of implicit prefix for GFX decode names and prefix them all * Get rid of special macro for adding GFXDECODE in favour of constructor * Make empty GFX decode a static member of interface * Allow palette to be specified to GFXDECODE as a device finder * Removed diserial.h from emu.h as it's used relatively infrequently Also fix darkseal and vaportra propely. The palette device automatically attaches itself to a share with matching tag. The correct solution here is to rename one or the other out of the way, since it was never attached to a share before.
* Removed DRIVER_INIT-related macros, made driver init entry in GAME/COMP/CONS ↵ MooglyGuy2018-05-131-61/+61
| | | | | | | | | | | | explicit. (#3565) * -Removed DRIVER_INIT macros in favor of explicitly-named member functions, nw * -Removed DRIVER_INIT_related macros. Made init_ prefix on driver initializers explicit. Renamed init_0 to empty_init. Fixed up GAME/COMP/CONS macro spacing. [Ryan Holtz] * Missed some files, nw * Fix compile, (nw)
* dsp16: fix condition mask in disassembler (nw) Vas Crabb2018-05-091-1/+1
| | | | (nw) remove more MCFG macros and make speaker config more explicit
* Cut/paste mistake (nw) AJR2018-05-061-1/+1
|
* ppu2c0x: Change NMI to line callback (nw) AJR2018-05-061-1/+2
|
* ppu2c0x family: Make palette internal to device AJR2018-05-061-5/+2
|
* Streamline machine configuration macros - everyone's a device edition. Vas Crabb2018-05-061-15/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Start replacing special device macros with additional constructors, starting with ISA, INTELLEC 4 and RS-232 buses. Allow an object finder to take on the target of another object finder. (For a combination of the previous two things in action, see either the INTELLEC 4 driver, or the Apple 2 PC Exporter card. Also check out looping over a device finder array to instantiate devices in some places. Lots of things no longer need to pass tags around.) Start supplying default clocks for things that have a standard clock or have all clocks internal. Eliminate the separate DEV versions of the DEVCB_ macros. Previously, the plain versions were a shortcut for DEVICE_SELF as the target. You can now supply a string tag (relative to current device being configured), an object finder (takes on the base and relative tag), or a reference to a device/interface (only do this if you know the device won't be replaced out from under it, but that's a safe assumption for your subdevices). In almost all cases, you can get the effect you want by supplying *this as the target. Eliminate sound and CPU versions of macros. They serve no useful purpose, provide no extra checks, make error messages longer, add indirection, and mislead newbies into thinking there's a difference. Remove a lot of now-unnecessary ":" prefixes binding things relative to machine root. Clean up some miscellaneous rot. Examples of new functionality in use in (some more subtle than others): * src/mame/drivers/intellec4.cpp * src/mame/drivers/tranz330.cpp * src/mame/drivers/osboren1.cpp * src/mame/drivers/zorba.cpp * src/mame/devices/smioc.cpp * src/devices/bus/a2bus/pc_xporter.cpp * src/devices/bus/isa/isa.h * src/devices/bus/isa/isa.h * src/devices/bus/intellec4/intellec4.h
* Standardise on IPT_CUSTOM for hooking up custom code in PORT_BIT, leaving ↵ smf-2018-04-031-1/+1
| | | | IPT_SPECIAL for the UI. [smf]
* nss.cpp, playch10.cpp: Replace MCFG_CPU_VBLANK_INT with line callbacks (nw) AJR2018-03-281-8/+10
|
* Restrict ROM labels to a filesystem- and shell-safe subset of printable Vas Crabb2018-03-181-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ASCII. This has not been done unilaterally - I have the support of @galibert, @Tafoid, and @rb6502 to do something about the current free-for-all. The trouble with the ROM label field in MAME is that it serves multiple competing purposes: it's supposed to identify the device in the original system, and also act as a filename when searching for media image files to load. It also has to appear in listings of needed/missing files (e.g. in cases where the image _isn't_ found). To identify the original device, the ROM label field in MAME often contains text derived from some combination of one or more of the text on a label if present, the silkscreen on an IC package, the location on the circuit board, and the device designation. There's no standard for the order in which these appear and how they're separated. Some people add arbitrary filename extensions and other annotations. There are practical limitations on what can appear in the string, given it's used as a filename: * Path/name length limits. * Restrictions on characters that can appear in a filename. * Practicality of using the filename in a command-line environment. * Ambiguity when describing a filename. Filesystems themselves typically restrict characters in filenames: * Windows defines MAX_PATH as 260 characters - longer paths are difficult to use with Win32 APIs and don't work properly in Windows Explorer * Most filesystems don't allow ^@ or the path separator in names. * Windows doesn't allow C0 control characters or <>:"/\|?* characters in filenames. * Filesystems may have collation, e.g. FAT16 is case-folding, NTFS and HFS+ are case-preserving but case-insensitive, while EXT and XFS are case-sensitive. * Filesystems may perform Unicode normalisation, e.g. NTFS forces NFC, HFS+ forces NFD, while ZFS stores filenames as supplied at creation, but may be configured to apply normalisation when testing equality. Shells use various ASCII characters for special purposes: * C0 control characters for line editing and control (e.g. ^C to cancel a line, ^V for control charecter escape, ^R for history search). * The "'\ chracaters for quoting/escaping. * The ><| characters for redirection. * The *?[] characters for pattern matching. * The ${}~ characters for variable substitution/sequence expansion. * The ! or ^ characters for history substitution. * The ()` characters for controlling subshells. * The %& characters for job control. * The ; character as a command separator. * The # character for comments. There's also the issue of whether users across a range of locales will be able to type/display characters. We still don't have good support for Unicode console output on Windows (std::wcout doesn't seem to work properly), many users don't install C/J/K fonts, and many users aren't comfortable entering text in unfamiliar languages. This means we're limited to printable ASCII for practical purposes. The practical limitations mean the subset of "safe" characters is limited to ASCII digits, either uppercase or lowercase English Latin (but not both due to collation behaving differently across systems), and the +,-.=_ punctuation chracters. We've decided on lowercase, digits, and safe punctuation. In addition to this, spaces are allowed, as they can be quoted/escaped easily enough if no other special characters are used. There have been some arguments that allowing uppercase is "more accurate", but in practical terms it doesn't add much value. A string in a C++ program can't represent layout, relative size of text, colour and shape of the label, text font, graphics, and many other details. It also does nothing to address labels with text outside the English Latin alphabet (e.g. labels with Chinese ideographs). Besides missing information, the lack of hard and fast rules means you need to intuit what a label string in MAME is trying to represent. There is simply no substitute for photographs. There wasn't even any consistency in case within individual machine sets. For example, several games in vigilant.cpp had inconsistent case for "ic" vs "IC" in designation suffixes, and ibm6850.cpp had inconsistent case for filename extensions withing a set. There were sets that used uppercase for text from the label but not from the part number/PCB location, and vice versa. It was a huge mess. There's some merit to the idea of allowing a wider variety of characters in the label strings in the source, and mapping to a more restricted set when searching for files. However it creates more issues than it solves. It would require a change to the XML output to provide both the label and filename, and a corresponding change to external ROM management tools. It would be impractical to do for software lists, because it would require ROM management tools to implement the exact same mapping algorithm as MAME. But that aside, actually doing useful mapping would be impractical. What would you do with C/J/K ideographs, like the chip labelled 東方不敗 (Dongfang Bubai)? There's no intuitive way to do the mapping wtihout incluing something like Unihan data, which would add a lot of bloat. Even the, without a language hint the Romanisation would be less than ideal in many cases (using Chinese reading for Japanese text and vice versa). There's still the messy issue of filesystem collation to deal with. We do allow full Unicode in comments in the source. If you want to provide a more detailed description of a ROM label, that's the place for it. You've got more characters available, and the possibility of using mulitple lines. There are too many other competing requirements on the label field in the ROM definitions.
* Address maps macros removal, pass 1 [O. Galibert] Olivier Galibert2018-03-141-28/+31
|
* nes_apu: Make it slightly less horrible [O. Galibert] Olivier Galibert2018-03-121-3/+0
|
* Remove first_screen(), nw Ryan Holtz2018-03-111-0/+3
|
* (nw) screw you macros and the horse you rode in on Vas Crabb2018-02-141-2/+4
| | | | | | There's no voodoo involved in derived machine configurations and fragments any more. The macros were just obfuscating things at this point.
* API change: Memory maps are now methods of the owner class [O. Galibert] Olivier Galibert2018-02-121-3/+3
| | | | | Also, a lot more freedom happened, that's going to be more visible soon.
* AM_SHARE not needed here (nw) Vas Crabb2018-01-281-2/+1
|
* playch10: expose countdown LEDs through output system and render with artwork Vas Crabb2018-01-271-5/+5
|