summaryrefslogtreecommitdiffstatshomepage
path: root/src/mame/drivers/m5.cpp (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Rearrange source to match project structure (done using the script in ↵ Vas Crabb2022-06-271-1690/+0
| | | | src/tools).
* init vars for coverity (drivers/l,m) Robbbert2022-03-261-2/+2
|
* Future-proofing by using correct #include for SOFTWARE_LIST device AJR2022-01-031-1/+1
|
* floppies: Turn the format arrays into function calls. Create a default ↵ Olivier Galibert2021-03-021-13/+11
| | | | "mfm", "fm" and "pc" list of formats. Their contents, and which driver uses what, may need some tuning.
* seta.cpp: Eliminate strcmp for per-game hacks AJR2020-12-041-5/+5
|
* m5.cpp: Updates and fixes AJR2020-12-031-242/+315
| | | | | | | | | - Install main ROM and RAM directly - Disable the 64K expansions (all already marked as unsupported) for now - Add clock for CTC channel 2 - brno: Add 8251 SIO and serial port - brno: Make RAM size configurable - Modernize various bits of code
* m5.cpp: Correct clocks AJR2020-12-031-6/+6
|
* emumem: Simplify memory management. [O. Galibert] Olivier Galibert2020-11-021-30/+30
| | | | | | | | | | | | | | | | | | | | 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
* m5: Put backslash on the correct key Robbbert2020-09-211-1/+1
|
* drivers starting with m, n and o: removed read* and write* macros (nw) Ivan Vangelista2020-06-121-20/+20
|
* Various buses and associated drivers: Simplify handler signatures (nw) AJR2020-05-211-7/+7
|
* more macro removal (nw) Ivan Vangelista2020-05-191-5/+5
|
* input_buffer, output_latch, z80dma: Eliminate now-unnecessary bus_r and ↵ AJR2020-03-181-2/+2
| | | | bus_w handlers (nw)
* Make devdelegate more like devcb for configuration. This is a Vas Crabb2019-10-261-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fundamental change to show device delegates are configured. Device delegates are now aware of the current device during configuration and will resolve string tags relative to it. This means that device delegates need a device to be supplied on construction so they can find the machine configuration object. There's a one-dimensional array helper to make it easier to construct arrays of device delegates with the same owner. (I didn't make an n-dimensional one because I didn't hit a use case, but it would be a simple addition.) There's no more bind_relative_to member - just call resolve() like you would for a devcb. There's also no need to cast nullptr when creating a late bind device delegate. The flip side is that for an overloaded or non-capturing lambda you'll need to cast to the desired type. There is one less conditional branch in the hot path for calls for delegates bound to a function pointer of member function pointer. This comes at the cost of one additional unconditional branch in the hot path for calls to delegates bound to functoids (lambdas, functions that don't take an object reference, other callable objects). This applies to all delegates, not just device delegates. Address spaces will now print an error message if a late bind error is encountered while installing a handler. This will give the range and address range, hopefully making it easier to guess which memory map is faulty. For the simple case of allowing a device_delegate member to be configured, use a member like this: template <typename... T> void set_foo(T &&...args) { m_foo_cb.set(std::forward<T>(args)...); } For a case where different delegates need to be used depending on the function signature, see src/emu/screen.h (the screen update function setters). Device delegates now take a target specification and function pointer. The target may be: * Target omitted, implying the current device being configured. This can only be used during configuration. It will work as long as the current device is not removed/replaced. * A tag string relative to the current device being configured. This can only be used during configuration. It will not be callable until .resolve() is called. It will work as long as the current device is not removed/replaced. * A device finder (required_device/optional_device). The delegate will late bind to the current target of the device finder. It will not be callable until .resolve() is called. It will work properly if the target device is replaced, as long as the device finder's base object isn't removed/replaced. * A reference to an object. It will be callable immediately. It will work as long as the target object is not removed/replaced. The target types and restrictions are pretty similar to what you already have on object finders and devcb, so it shouldn't cause any surprises. Note that dereferencing a device finder will changes the effect. To illustrate this: ... required_device<some_device> m_dev; ... m_dev(*this, "dev") ... // will late bind to "dev" relative to *this // will work if "dev" hasn't been created yet or is replaced later // won't work if *this is removed/replaced // won't be callable until resolve() is called cb1.set(m_dev, FUNC(some_device::w)); ... // will bind to current target of m_dev // will not work if m_dev is not resolved // will not work if "dev" is replaced later // will be callable immediately cb2.set(*m_dev, FUNC(some_device::w)); ... The order of the target and name has been reversed for functoids (lambdas and other callable objects). This allows the NAME macro to be used on lambdas and functoids. For example: foo.set_something(NAME([this] (u8 data) { m_something = data; })); I realise the diagnostic messages get ugly if you use NAME on a large lambda. You can still give a literal name, you just have to place it after the lambda rather than before. This is uglier, but it's intentional. I'm trying to drive developers away from a certain style. While it's nice that you can put half the driver code in the memory map, it detracts from readability. It's hard to visualise the memory range mappings if the memory map functions are punctuated by large lambdas. There's also slightly higher overhead for calling a delegate bound to a functoid. If the code is prettier for trivial lambdas but uglier for non-trivial lambdas in address maps, it will hopefully steer people away from putting non-trivial lambdas in memory maps. There were some devices that were converted from using plain delegates without adding bind_relative_to calls. I fixed some of them (e.g. LaserDisc) but I probably missed some. These will likely crash on unresolved delegate calls. There are some devices that reset delegates at configuration complete or start time, preventing them from being set up during configuration (e.g. src/devices/video/ppu2c0x.cpp and src/devices/machine/68307.cpp). This goes against the design principles of how device delegates should be used, but I didn't change them because I don't trust myself to find all the places they're used. I've definitely broken some stuff with this (I know about asterix), so report issues and bear with me until I get it all fixed.
* (nw) removed every remaining AM_ macro I could find in comments, but one in ↵ Ivan Vangelista2019-10-101-3/+3
| | | | emu\memarray.h cause I didn't want to cause a full recompile for this (nw)
* (nw) get rid of wave.h usage part 1 Robbbert2019-07-061-2/+1
|
* -snapquik: Modernized delegate and removed MCFG macros. [Ryan Holtz] MooglyGuy2019-06-301-1/+1
|
* (nw) more cassette wave sound Robbbert2019-06-301-0/+2
|
* (nw) Clean up the mess on master Vas Crabb2019-03-261-39/+36
| | | | | | | | | | | | | 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-36/+39
| | | | | This reverts commit c24473ddff715ecec2e258a6eb38960cf8c8e98e, reversing changes made to 009cba4fb8102102168ef32870892438327f3705.
* tms9928a, v9938: Remove space and mem_mask from read/write handlers (nw) AJR2019-03-091-4/+2
| | | | efo90501: Tweak dots per line to get closer to typical PAL rates (nw)
* mame\drivers: removed most MCFG and MACHINE_CONFIG macros from drivers ↵ Ivan Vangelista2019-02-261-4/+4
| | | | starting with m, n and o (nw)
* sn76496.cpp : Remove unnecessary handler, Remove unnecessary arguments in ↵ cam9002019-02-021-2/+2
| | | | | | stereo_w write8smo handler is already exists (write)
* devices\bus: some more MCFG macros removal (nw) Ivan Vangelista2019-02-011-9/+9
|
* emu\softlist_dev: removed MCFG macros (nw) Ivan Vangelista2019-01-301-7/+7
| | | | also removed MCFG_DEVICE_REMOVE, MCFG_QUANTUM_TIME and MCFG_QUANTUM_PERFECT_CPU (nw)
* src/mame: removed all instances of MCFG_DEVICE_REMOVE in the mame part of ↵ Ivan Vangelista2019-01-291-1/+1
| | | | the tree (nw)
* output_latch: removed MCFG macros (nw) Ivan Vangelista2019-01-291-3/+4
|
* imagedev\floppy: removed MCFG macros (nw) Ivan Vangelista2019-01-281-5/+3
|
* magedev\cassette: removed MCFG macros (nw) Ivan Vangelista2019-01-221-4/+4
|
* upd765: Add (mostly standard) clocks to all devices in the family (nw) AJR2018-12-131-1/+1
| | | | These clocks are currently unused, and their sources and dividers are often unclear. In some cases they are clearly software-configurable, which has not been emulated at all.
* pc_lpt, upd765: removed MCFG macros (nw) Ivan Vangelista2018-09-281-6/+6
|
* wd_fdc: removed MCFG macros (nw) Ivan Vangelista2018-09-061-1/+1
|
* -i8255: Removed MCFG, nw mooglyguy2018-09-031-6/+6
|
* z80ctc: removed MCFG macros (nw) Ivan Vangelista2018-09-031-2/+2
|
* z80daisy_generic, z80dart, z80dma: removed MCFG macros (nw) Ivan Vangelista2018-08-301-9/+6
| | | | z80_daisy: first part of MCFG macro removal (nw)
* tms9928a: Configuration modernization (nw) AJR2018-08-211-20/+21
| | | | | | | | | | | | | - Replace callback configuration macros with devcb3 (slightly shortening function names in the process) - Change configured clock to be twice the dot clock (as on hardware), rather than equal to it - Allow the VDP to configure the screen in device_config_complete (taking into account 60 Hz/50 Hz variations), making MCFG_TMS9928A_SCREEN_ADD_NTSC/_PAL macros obsolete - Add notes on clock outputs msx.cpp: Use a template to simplify configuration of all the MSX1 VDP variants (nw) bbcbc: Increase clock speed to a more plausible rate WARNING: Withheld for now due to Vas's quibbles with the similar approach used in 577f198564faff49f2636600598a15644db354bb.
* -ram_device: MCFG removal, nw mooglyguy2018-08-161-3/+2
|
* Made a pass over the source to eliminate uppercase hex in hashes (nw) Scott Stone2018-07-131-1/+1
|
* acro removal, disambiguation, debugger side effects (nw) Vas Crabb2018-06-151-1/+1
|
* as if millions of this pointers suddenly cried out in terror, and were ↵ Vas Crabb2018-06-081-23/+23
| | | | | | | 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-271-8/+8
|
* proposal: move z80daisy* to devices/machine (#3572) Patrick Mackinlay2018-05-151-1/+1
| | | | | | | | | | * proposal: move z80daisy* to devices/machine Seems to me this is a machine, not a CPU? Main reason was to stop the Z80 CPU from being dragged into systems that don't have one just because they use a Z80 family peripheral. * missed this one (nw) * missed a spot (nw)
* Removed DRIVER_INIT-related macros, made driver init entry in GAME/COMP/CONS ↵ MooglyGuy2018-05-131-7/+7
| | | | | | | | | | | | 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-19/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-10/+13
| | | | | | | | | | | | | | | | | | | | | * 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.
* Address maps macros removal, pass 1 [O. Galibert] Olivier Galibert2018-03-141-86/+92
|
* (nw) screw you macros and the horse you rode in on Vas Crabb2018-02-141-5/+8
| | | | | | 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-6/+6
| | | | | Also, a lot more freedom happened, that's going to be more visible soon.
* xtal.h is dead, long live to xtal.cpp [O. Galibert] Olivier Galibert2018-01-231-8/+8
|