summaryrefslogtreecommitdiffstatshomepage
path: root/src/mame/drivers/gei.cpp (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Rearrange source to match project structure (done using the script in ↵ Vas Crabb2022-06-271-2073/+0
| | | | src/tools).
* - gei.cpp: document how to clear remaining credits [Brian Troha] Ivan Vangelista2022-03-041-0/+5
| | | | | | | | - model2.cpp: fill in Rail Chase 2's Sega ID & ROM board info [Brian Troha] - model3.cpp: add Spikeout security module number and correct game ID & ROM board ID for Virtua Striker 2 Ver98 Step2 [Brian Troha] - system1.cpp: add Sega game ID to SWAT [Brian Troha]
* gei.cpp: correct DIP switches for gtsers12a and gtsers14a (MT08198) (#9259) Steven Coomber2022-02-031-2/+2
|
* volt_reg: Remove uses that are not needed anymore with the recent (#7367) Aaron Giles2020-10-201-3/+0
| | | DAC changes. Which is all of them. Remove the device as well.
* Cleaned up bitmap API. Vas Crabb2020-09-271-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Made const-qualified pixel accessors (pix, pixt, raw_pixptr) return const-qualified references/pointers to pixesl, and added non-const versions. This makes bitmap more like standard library containers where const protects the content as well as the dimensions. Made the templated pixt accessor protected - having it public makes it too easy to inadvertently get a pointer to the wrong location. Removed the pix(8|16|32|64) accessors from the specific bitmaps. You could only use the "correct" one anyway, and having the "incorrect" ones available prevented explicit instantiations of the class template because the static assertions would fail. You can still see the pixel type in the bitmap class names, and you can't assign the result of &pix(y, x) to the wrong kind of pointer without a cast. Added fill member functions to the specific bitmap template, and added a explicit instantiations. This allows the bitmap size check to be skipped on most bitmap fills, although the clipping check is still there. Also fixed a couple of places that were trying to fill an indexed 16-bit bitmap with rgb_t::black() exposed by this (replaced with zero to get the same net effect). The explicit template instantiations in the .cpp file mean the compiler can inline the function if necessary, but don't need to generate a local out-of-line body if it chooses not to. Extended the size of the fill value parameter in the base bitmap class to 64 bits so it works correctly for 64-bit bitmaps. Fixed places where IE15 and VGM visualiser weren't accounting for row bytes potentially being larger than width. Fixed an off-by-one in an HP-DIO card where it was treating the Topcat cursor right edge as exclusive. Updated everything to work with the API changes, reduced the scope of many variables, added more const, and replaced a few fill/copy loops with stuff from <algorithm>.
* srcclean and cleanup (nw) Vas Crabb2020-06-211-3/+3
|
* (nw) gei.cpp: Singular VS. plural braintro2020-06-141-13/+13
|
* New working clones braintro2020-06-141-77/+156
| | | | | | | | | | | | | | | New working clones ------------------ Trivia (Questions Series 12 Alt Question Rom) Trivia (Questions Series 14 Alt Question Rom) Trivia (Version 1.03a Sex questions, Alt revision questions) gei.cpp: Documented Trivia sets series 12 through 19. [Brian Troha] out of whatsnew: Sorted out question ROMs as per documentation results in 3 new clones. Add lots of misc information to various sets. correct a couple of comments.
* drivers starting with f, g and h: some macro removal (nw) Ivan Vangelista2020-05-271-15/+15
|
* a little more macro removal (nw) Ivan Vangelista2020-05-181-12/+12
|
* (nw) Clean up the mess on master Vas Crabb2019-03-261-54/+55
| | | | | | | | | | | | | This effectively reverts b380514764cf857469bae61c11143a19f79a74c5 and c24473ddff715ecec2e258a6eb38960cf8c8e98e, restoring the state at 598cd5227223c3b04ca31f0dbc1981256d9ea3ff. Before pushing, please check that what you're about to push is sane. Check your local commit log and ensure there isn't anything out-of-place before pushing to mainline. When things like this happen, it wastes everyone's time. I really don't need this in a week when real work™ is busting my balls and I'm behind where I want to be with preparing for MAME release.
* Revert "conflict resolution (nw)" andreasnaive2019-03-251-55/+54
| | | | | This reverts commit c24473ddff715ecec2e258a6eb38960cf8c8e98e, reversing changes made to 009cba4fb8102102168ef32870892438327f3705.
* mame\drivers: removed most MCFG and MACHINE_CONFIG macros from drivers ↵ Ivan Vangelista2019-03-061-48/+49
| | | | starting with h and from the heavy hitters starting with g (nw)
* volt_reg: set default m_output (nw) hap2019-02-191-1/+0
|
* misc MCFG and MACHINE_CONFIG macro removal (nw) Ivan Vangelista2019-02-131-1/+1
|
* volt_reg: removed MCFG macro (nw) Ivan Vangelista2019-02-121-2/+3
|
* devices\machine\ticket, timer: removed MCFG macros (nw) Ivan Vangelista2019-01-211-3/+3
|
* Mark empty PLD dumps from protected devices as NO_DUMP (nw) (#4407) ClawGrip2018-12-281-5/+5
| | | | | | | | | | | | | | | | | | | | | | * goldstar.cpp: Mark empty PLD dumps from protected devices as NO_DUMP (nw) * igs009.cpp: Mark empty PLD dumps from protected devices as NO_DUMP (nw) * kingdrby.cpp: Mark empty PLD dumps from protected devices as NO_DUMP (nw) * funworld.cpp: Mark empty PLD dumps from protected devices as NO_DUMP (nw) * system16.cpp: Mark empty PLD dumps from protected devices as NO_DUMP (nw) * jackie.cpp: Mark empty PLD dumps from protected devices as NO_DUMP (nw) * gaiden.cpp: Mark empty PLD dumps from protected devices as NO_DUMP (nw) * polepos.cpp: Mark empty PLD dumps from protected devices as NO_DUMP (nw) * gei.cpp: Mark empty PLD dumps from protected devices as NO_DUMP (nw) * vsnes.cpp: Mark empty PLD dumps from protected devices as NO_DUMP (nw)
* Start cleaning up palette configuration: Vas Crabb2018-12-291-3/+2
| | | | | | | | | | * 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.
* -i8255: Removed MCFG, nw mooglyguy2018-09-031-43/+33
|
* -nvram: Removed MCFG, nw mooglyguy2018-08-241-1/+1
|
* more private member use in 'D, E, F, G' drivers (nw) (#3704) David Haywood2018-06-271-17/+18
| | | | | | | | | | | | * more private member use in 'D' drivers (nw) * same for 'E' drivers (nw) * and 'F' (nw) * 'G' (nw) (left galaxian/galaxold alone because I know somebody is looking at them)
* Remove emupal.h from emu.h (nw) AJR2018-06-131-0/+1
|
* as if millions of this pointers suddenly cried out in terror, and were ↵ Vas Crabb2018-06-081-66/+66
| | | | | | | 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
* use plural names for output finders when there are multiple outputs (#3595) wilbertpol2018-05-271-18/+18
| | | | | | | | * use plural names for output finders when there are multiple outputs (nw) * use plural names for output finders when there are multiple outputs (nw) * use plural names for output finders when there are multiple outputs (nw)
* Replace set_led_value and set_lamp_value with output_finders. [Wilbe… (#3592) wilbertpol2018-05-201-22/+26
| | | | | | * Replace set_led_value and set_lamp_value with output_finders. [Wilbert Pol] * segaufo: keep the 2 bit lamp outputs
* diexec: Interrupt API changes (nw) AJR2018-05-181-1/+1
| | | | | | - 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.
* Removed DRIVER_INIT-related macros, made driver init entry in GAME/COMP/CONS ↵ MooglyGuy2018-05-131-73/+73
| | | | | | | | | | | | 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
* Streamline machine configuration macros - everyone's a device edition. Vas Crabb2018-05-061-30/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Make MCFG_DEVICE_ADD and callable device types more flexible: Vas Crabb2018-05-041-1/+1
| | | | | | | | | | | | | | | | | | | | | * Allows defaulted clocks (see subtle example with vboy) * Allows additional constructors (see RS232 port in tranz330) * Allows use of device finder in place of tag in MCFG_DEVICE_ADD * Requires out-of-line destructor for devices using incomplete types * Requires XTAL or explicit u32 for clocks for devices with private types Devices must still define the standard constructor. When writing additional constructors, be aware that the constructor runs before device_add_mconfig in the context of the existing device, not the new device. See osborne1, zorba, tranz330, and vboy for examples of this in use. Compilation is a bit slower, but this is temporary while refactoring is in progress. Eliminated the need for MCFG_SOUND_ROUTE_EX. Removed macros from slot option configuration - they just obfuscated code and slowed it down with needless dynamic casts, but didn't actually simplify it.
* Standardise on IPT_CUSTOM for hooking up custom code in PORT_BIT, leaving ↵ smf-2018-04-031-2/+2
| | | | IPT_SPECIAL for the UI. [smf]
* Restrict ROM labels to a filesystem- and shell-safe subset of printable Vas Crabb2018-03-181-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-147/+156
|
* Grammar police (nw) Olivier Galibert2018-02-241-1/+1
|
* (nw) screw you macros and the horse you rode in on Vas Crabb2018-02-141-9/+18
| | | | | | 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-9/+18
| | | | | Also, a lot more freedom happened, that's going to be more visible soon.
* API change: Memory maps are now "last entry wins" [O. Galibert] Olivier Galibert2018-01-311-4/+4
| | | | | | | This allows for the much more natural "import another map and patch it" structure, or "cover a whole region then punch holes in it". Our previous first-entry-wins rule was always a surprise to newcomers, and oldcomers too.
* Misc stuff (nw) Olivier Galibert2018-01-271-1/+1
|
* API Change: Machine configs are now a method of the owner class, and the ↵ Olivier Galibert2018-01-171-10/+20
| | | | | | | | | | prototype is simplified [O. Galibert] Beware, the device context does not follow in MCFG_FRAGMENT_ADD anymore due to the prototype change. So creating a device then configuring through a fragment doesn't work as-is. The simplest solution is just to add a MCFG_DEVICE_MODIFY at the start of the fragment with the correct tag.
* This causes huge changes in behaviour that can't be hand-waved away. Vas Crabb2018-01-131-1/+3
| | | | | | | | | | Revert "Removal of voltage_regulator_device (nw)" This reverts commit 1af133752a05079060c462e372c369ad0b7296ee. Revert "New way to provide DAC reference inputs (nw)" This reverts commit 1c6a7ab40ccd23b753777204c7a289e830b2adcb.
* New way to provide DAC reference inputs (nw) AJR2018-01-101-3/+1
| | | | | | | - Introduce MCFG_SOUND_REFERENCE_INPUT to provide fixed inputs through the resampler, eliminating the need for the "voltage regulator" device - Replace memset use in sound.cpp with std::fill This was my third implementation of this concept. The previous two involved attaching sound streams to the dummy device (which required giving it device_sound_interface and other modifications).
* Do the easy ones (nw) Olivier Galibert2018-01-011-1/+1
|
* Revert "Revert "Merge branch 'master' of https://github.com/mamedev/mame"" Firehawke2017-12-131-2/+2
| | | | This reverts commit 54155441e9ba9941e85d80c4834a66376a11e791.
* Revert "Merge branch 'master' of https://github.com/mamedev/mame" Firehawke2017-12-131-2/+2
| | | | | This reverts commit f537428e5a40ba6dde8ca9bf0fe9ae6b1f189ac4, reversing changes made to 0d70d798107d4e4e8fb9f230410aeb1e888d65c5.
* ticket.cpp: Eliminate legacy write method and "active bit" nonsense (nw) AJR2017-12-061-2/+2
|
* gei.cpp: cleanup (nw) Vas Crabb2017-11-091-169/+63
|
* gei.cpp: fixed MT04651 (nw) Ivan Vangelista2017-11-071-20/+7
|
* gei.cpp: misc refactoring: (nw) Ivan Vangelista2017-10-311-218/+253
| | | | | | | * moved 'signatures' out of the source and into a ROM, as suggested; * switched to configured banking; * added save state support; * added default nvrams to some of the sets to avoid errors on first boot.
* gei.cpp: Counting is hard ;-p (nw) briantro2017-10-301-3/+3
|