summaryrefslogtreecommitdiffstatshomepage
path: root/src/devices/bus/ti99/peb
Commit message (Collapse)AuthorAgeFilesLines
...
* turn back into an array (nw) Vas Crabb2018-08-212-89/+19
|
* ti99: Kill some more MCFGs. (nw) Michael Zapf2018-08-213-32/+23
|
* ti99: Adapting to common devcb3 slot device handling. (nw) Michael Zapf2018-08-203-120/+136
|
* ti99: Minor config changes, simplified ti99 config, use new cassette output. Michael Zapf2018-08-191-1/+0
|
* ti99: Further devcb3 works (nw). Michael Zapf2018-08-186-36/+51
|
* tms99xx: Various devcb3 updates. (nw) Michael Zapf2018-08-182-121/+83
|
* -ram_device: MCFG removal, nw mooglyguy2018-08-167-42/+23
|
* -amigafdc, at29x, at45dbxx, at_keybc, ataintf, atmel_arm_aic, pci-ide: MCFG ↵ mooglyguy2018-08-153-17/+22
| | | | removal, nw
* ti99: devcb3 for the slot devices (nw) Michael Zapf2018-08-133-171/+152
|
* -7200fifo, 7400, 7404, 74123, 74145, 74148, 74153, 74157, 74161, 74259: ↵ mooglyguy2018-08-114-24/+24
| | | | | | | | [Ryan Holtz] * Removed MCFG and old devcb macros. AJR, any breakage? nw
* ti99: Steps towards devcb3, wip. (nw) Michael Zapf2018-08-117-48/+109
|
* ti99: Modernized logging. (nw) Michael Zapf2018-08-1113-400/+378
|
* wd_fdc: Simplify API. Plus some collateral damage [O. Galibert] Olivier Galibert2018-08-102-4/+4
|
* devcb3 Vas Crabb2018-07-071-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* ti99: Removed deprecated function calls, simplified GROM access, added ↵ Michael Zapf2018-06-304-16/+15
| | | | logmacro. (nw)
* geneve: Using bios selection; split genmod as a separate driver Michael Zapf2018-06-102-23/+49
|
* as if millions of this pointers suddenly cried out in terror, and were ↵ Vas Crabb2018-06-081-1/+1
| | | | | | | 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
* wd_fdc family, msm5832: Eliminate customized MCFG_XXX_ADD macros (nw) AJR2018-05-272-2/+2
|
* dsp16: fix condition mask in disassembler (nw) Vas Crabb2018-05-092-2/+2
| | | | (nw) remove more MCFG macros and make speaker config more explicit
* Streamline machine configuration macros - everyone's a device edition. Vas Crabb2018-05-069-53/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-044-77/+85
| | | | | | | | | | | | | | | | | | | | | * 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.
* destaticify initializations (nw) (#3289) wilbertpol2018-03-041-8/+8
| | | | | | * destaticify initializations (nw) * fix this->set_screen (nw)
* Grammar police (nw) Olivier Galibert2018-02-249-21/+21
|
* xtal.h is dead, long live to xtal.cpp [O. Galibert] Olivier Galibert2018-01-233-4/+4
|
* API Change: Machine configs are now a method of the owner class, and the ↵ Olivier Galibert2018-01-1716-19/+19
| | | | | | | | | | 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.
* ATA: Simplified class hierarchy so there is no ambiguity with 16 & 32 bit ↵ smf-2017-12-201-4/+4
| | | | methods. Removed the memory system read/write handler trampolines from the ATA devices as they are not required. (nw)
* ide: Add non-space cs access methods, use them wherever possible [O. Galibert] Olivier Galibert2017-12-161-4/+4
|
* ide: deambiguate cs access between 16 and 32 bits [O. Galibert] Olivier Galibert2017-12-161-4/+4
|
* Remove timer_device from emu.h and move it out of src/emu (nw) AJR2017-10-011-0/+1
|
* samsmem.cpp: Add 74LS259 (nw) AJR2017-07-312-6/+21
|
* New 74LS259/9334/CD4099 devices AJR2017-07-256-159/+201
| | | | | | | | These humble 16-pin logic devices were commonly used in 8-bit arcade games to control coin counters/lockouts, IRQ flipflops, graphics banking, slave CPU reset lines, discrete audio triggers, screen flipping, serial EEPROMs and much else. Over 100 drivers and a few bus devices have been updated to use the new implementation, and a great deal of research has gone into documenting the physical location of these devices on actual PCBs in the source. Write handlers have been provided for both orthodox and somewhat less conventional memory mappings. Incidental to this update, coin counters and/or lockouts have been added to Atari System 1 games, Basketball, Gauntlet, Gyruss, Hana Yayoi, Hole Land, Jr. Pac-Man, Mahjong Sisters, Pooyan, Roc'n Rope, Squash, Thunder Hoop, Time Limit, Time Pilot '84 and many others. This also cleans up coin counter behavior in Sauro and Rally Bike. (nw) The purpose of committing this change, which has been several months in the making, early in the 0.189GIT cycle will be to allow time for fixing potential regressions; I've fixed a number of drivers that lost sound from this for various reasons (hnayayoi.cpp having missing or garbage ADPCM was particularly painful, since the three games in that driver all work slightly differently), but I can't test all affected drivers exhaustively. @Tafoid, don't bother running automated screen capture comparison tests on this, as many drivers are now expected to have the screen flipped for the first few seconds after reset.
* samsmem.cpp: fixed MT06564 (nw) Ivan Vangelista2017-07-061-2/+2
|
* finally got rid of machine_mconfig_additions (nw) Ivan Vangelista2017-06-1430-210/+139
|
* ti99: Architectural cleanup for slot devices; constant renaming Michael Zapf2017-06-0832-176/+218
|
* fix ti99_4p blowing up (evpc and hsgpl missing from peb card choices) (nw) Vas Crabb2017-05-282-69/+51
|
* ti99: Change ioport default to peb for ti99_4ev, also add evpc automatically Michael Zapf2017-05-272-17/+55
|
* Validation fix for peribox (nw) AJR2017-05-251-1/+1
|
* ti99: Added console connector "ioport" with PEB as slot option Michael Zapf2017-05-252-136/+88
|
* ti99: Wrapped into namespaces; minor rearrangement Michael Zapf2017-05-2332-58/+189
|
* Goodbye MACHINE_CONFIG_FRAGMENT, it was nice knowing you. Vas Crabb2017-05-2216-20/+20
| | | | | | | | | (nw) This is a pretty minimal change. The point where the root device is added has been moved from the MACHINE_CONFIG_START macro to the constructor of the machine configuration class (made possible by giving drivers their own device types). This isn't the final change in this area. The root device is still being handled specially in that its configuration comes from the game driver structure. This needs to be harmonised with regular devices. But that's a job for another day.
* Fix crashes in -listxml in debug builds Vas Crabb2017-05-211-12/+4
| | | | | | | | | | | | | | | | | * Make -listxml instantiate slot devices in slots rather than under the machine root * Use dynamic_cast rather than static_cast or downcast on parent device in TI-99 slot/card devices (nw) There are still very real issues present. When -listxml, -listroms, -verifyroms, etc. instantiate individual devices, they don't have the information necessary to instantiate the expected parent device. So slots won't be children of the bus they expect to be attached to, and cards won't be in their usual slots. It's unsafe to use static_cast<> on owner at the best of times, and doing anything with the result is likely to cause silent memory corruption during listxml (this was previously happening with the TI-99 peripheral box slot device). You can't use downcast<> at configuration complete time either, as that degenerates to a static_cast<> in release builds anyway, and it will cause a crash in -listxml in debug builds as we had before. The choices are to use a dynamic_cast and check the result before doing anything with it before device start time, or wait for device start time and use downcast<> at that point.
* Move static data out of devices into the device types. This is a ↵ Vas Crabb2017-05-1432-0/+9434
significant change, so please pay attention. The core changes are: * Short name, full name and source file are no longer members of device_t, they are part of the device type * MACHINE_COFIG_START no longer needs a driver class * MACHINE_CONFIG_DERIVED_CLASS is no longer necessary * Specify the state class you want in the GAME/COMP/CONS line * The compiler will work out the base class where the driver init member is declared * There is one static device type object per driver rather than one per machine configuration Use DECLARE_DEVICE_TYPE or DECLARE_DEVICE_TYPE_NS to declare device type. * DECLARE_DEVICE_TYPE forward-declares teh device type and class, and declares extern object finders. * DECLARE_DEVICE_TYPE_NS is for devices classes in namespaces - it doesn't forward-declare the device type. Use DEFINE_DEVICE_TYPE or DEFINE_DEVICE_TYPE_NS to define device types. * These macros declare storage for the static data, and instantiate the device type and device finder templates. The rest of the changes are mostly just moving stuff out of headers that shouldn't be there, renaming stuff for consistency, and scoping stuff down where appropriate. Things I've actually messed with substantially: * More descriptive names for a lot of devices * Untangled the fantasy sound from the driver state, which necessitates breaking up sound/flip writes * Changed DECO BSMT2000 ready callback into a device delegate * Untangled Microprose 3D noise from driver state * Used object finders for CoCo multipak, KC85 D002, and Irem sound subdevices * Started to get TI-99 stuff out of the TI-990 directory and arrange bus devices properly * Started to break out common parts of Samsung ARM SoC devices * Turned some of FM, SID, SCSP DSP, EPIC12 and Voodoo cores into something resmbling C++ * Tried to make Z180 table allocation/setup a bit safer * Converted generic keyboard/terminal to not use WRITE8 - space/offset aren't relevant * Dynamically allocate generic terminal buffer so derived devices (e.g. teleprinter) can specify size * Imporved encapsulation of Z80DART channels * Refactored the SPC7110 bit table generator loop to make it more readable * Added wrappers for SNES PPU operations so members can be made protected * Factored out some boilerplate for YM chips with PSG * toaplan2 gfx * stic/intv resolution * Video System video * Out Run/Y-board sprite alignment * GIC video hookup * Amstrad CPC ROM box members * IQ151 ROM cart region * MSX cart IRQ callback resolution time * SMS passthrough control devices starting subslots I've smoke-tested several drivers, but I've probably missed something. Things I've missed will likely blow up spectacularly with failure to bind errors and the like. Let me know if there's more subtle breakage (could have happened in FM or Voodoo). And can everyone please, please try to keep stuff clean. In particular, please stop polluting the global namespace. Keep things out of headers that don't need to be there, and use things that can be scoped down rather than macros. It feels like an uphill battle trying to get this stuff under control while more of it's added.