summaryrefslogtreecommitdiffstatshomepage
path: root/src/devices/machine/pdc.cpp
Commit message (Collapse)AuthorAgeFilesLines
* addrmap: Allow ioport finders in portr/w/rw Olivier Galibert2024-10-131-3/+5
| | | | | | | | | Convert a number of drivers to use ioport finders in the memory map. This is not entirely gratuitous. The idea is to ensure all the ports are in the class, so that eventually ioport finders become ioport creators. The ultimate aim is to C++-ify port descriptions which would be made way nicer by getting rid of the need for PORT_START.
* emu/devcb.h: Eliminated the need to call resolve() on callbacks. (#11333) Vas Crabb2023-06-171-5/+1
| | | | | | | | | | | | Read callbacks now need a default return value supplied at construction. Replaced isnull() with isunset() which tells you if the callback wasn't configured rather than whether it isn't safe to call. Enabled validation of device callbacks (it seems it was disabled at some point, probably accidentally). Device callbacks and object finders now implement the same interface for resolution.
* floppies: Turn the format arrays into function calls. Create a default ↵ Olivier Galibert2021-03-021-9/+1
| | | | "mfm", "fm" and "pc" list of formats. Their contents, and which driver uses what, may need some tuning.
* pdc.cpp: fixed 'm_functions.empty()' assert in debug builds (nw) Ivan Vangelista2020-04-021-4/+0
|
* devices/machine: simplified handlers for various devices (nw) Ivan Vangelista2020-03-241-18/+18
|
* (nw) Clean up the mess on master Vas Crabb2019-03-261-1/+2
| | | | | | | | | | | | | 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-2/+1
| | | | | This reverts commit c24473ddff715ecec2e258a6eb38960cf8c8e98e, reversing changes made to 009cba4fb8102102168ef32870892438327f3705.
* emu\softlist_dev: removed MCFG macros (nw) Ivan Vangelista2019-01-301-1/+1
| | | | also removed MCFG_DEVICE_REMOVE, MCFG_QUANTUM_TIME and MCFG_QUANTUM_PERFECT_CPU (nw)
* More progress towards ISA DACK line support (nw) AJR2019-01-201-0/+1
|
* 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.
* r9751: Implement proper SMIOC emulation through new uart emulation (#4188) Brandon Munger2018-10-241-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * [R9751] (Squashed) Early work on SMIOC emulation commit 9b587be762abfd576e92792c612cd205c570924d Author: Stephen Stair <sgstair@akkit.org> Date: Tue Apr 10 19:41:55 2018 -0700 Connected SMIOC DMA to 68k * SMIOC now reading bytes for serial from the 68k memory space successfully. commit 0f801a05a3fa5b78768a1a2bcb9981466e8f2b0e Author: Stephen Stair <sgstair@akkit.org> Date: Tue Mar 27 18:31:32 2018 -0700 68k now running in lockstep with SMIOC for serial * 68k now uses actual SMIOC as source of SMIOC status, so it waits for the SMIOC to complete commands before continuing. * SMIOC DMA controllers now being asked to move bytes around * "write character" (4100) commands to SMIOC are now completing and resulting in correct status being written and sent back to the 68k * Every now and then the SMIOC stalls for a bit, it seems to be due to spending some time trying to communicate with the 8051 CPU (used to communicate with another cpu on the serial breakout box) that is not currently present in the emulated device. Next Steps: * We're going to move the terminal from the r9751 into the SMIOC, and hook it up to the DMA controllers as a hacky temporary solution. * We need to emulate the 5xxxx memory range in SMIOC to proxy data to/from the 68k memory * Then we'll start work on emulating the octal uart properly and hooking it up to RS232 channels. commit ca91614fca3f43d87755d0c3439521276d7bfafb Author: Stephen Stair <sgstair@akkit.org> Date: Wed Mar 14 19:52:04 2018 -0700 Tinkering to get SMIOC further along 1) Enable 188 cpu to advance DMA immediatley if DRQ is held high when source synchronous DMA is started (It's not clear whether the DMA actually works this way yet) 2) Retrigger the DMA DRQ when a memory access is made to the DMA window (future work needed to proxy the reads/writes to the 68k's main memory) This is needed to support multibyte DMA reads/writes to the 68k window. 3) Reverse the bytes in the status register (based on current incomplete understanding of how this is encoded) 4) Connect the status register back to the r9751 on SMIOC status read Current state: SMIOC's main board DMA state machine now completes the DMA transfer from the main board (With incorrect data), but we are still getting stuck. Next steps: SMIOC is now hanging waiting on DMA to UART to complete, we need to implement some emulation of the UART and its connections to the surrounding 16 dma channels in order to make progress. commit 62c1455c97a53ed970622e08cb03a225625914fd Author: Stephen Stair <sgstair@akkit.org> Date: Sun Mar 4 20:13:32 2018 -0800 Progress on emulating SMIOC commit daee8498c5840417aee3ed9def0acfba5476335a Author: Stephen Stair <sgstair@akkit.org> Date: Sun Feb 25 20:02:32 2018 -0800 Working on bringing up SMIOC Trying to get emulated SMIOC in lockstep with the main 68k. commit 5a929fde90307040a0544682888f2f21a914b900 Author: Stephen Stair <sgstair@akkit.org> Date: Wed Feb 21 20:06:27 2018 -0800 re-enable SMIOC, Logging improvements, first steps towards emulating on-board hardware. commit f0c7a1665a18c99df5527ae45994f39f95223814 Author: Stephen Stair <sgstair@akkit.org> Date: Sun Feb 11 16:26:31 2018 -0800 Emulation fix - Terminal now responds to input commit ecff4035f3fdaa0329df46f99ccd516aa23ec8af Author: Stephen Stair <sgstair@akkit.org> Date: Tue Feb 6 19:00:35 2018 -0800 Hacky emulation of SMIOC now successfully receiving serial characters! commit 376bca90dff311d24e1f5014d8d6f0dc297bf671 Author: Stephen Stair <sgstair@akkit.org> Date: Sun Jan 28 18:31:38 2018 -0800 Experimenting with SMIOC emulation * Partial fixes for line state issues with persistent line values When the AM9517 DMA controller mode is updated to change the polarity of DACK/DREQ, it doesn't update the DACK line values / request values (respectively). This fixes this issue for one of the emulated devices in the file, but the other device has the same problem. * Add skeleton of SCC2698B UART device * Early progress on emulating SCC2698B Octal UART Core structure for IO lines and writing registers is in place. * Update address maps to new format. * SCC2698b: Add tx/rx, baud rate generation * Emulation improvements for scc2698b device * MPP output pins emulated * Improved logging for baud rate changes * Channel configuration emulated * Support for TX/RX Enable * Started integrating new features into SMIOC * Minor progress on the path to enabling new UART for SMIOC * Resolved code issues related to upstream changes * Working around an apparent problem with callbacks on sub-device devices * Terminal added for serial port attached to SCC2698B UART. * Things compile and seem to work. * SMIOC: Serial is now outputting correctly through emulated SMIOC Some glitches to work out, but this is nearly ready. * AM9517a should not forget about input line status on master reset. * Disable tracing * SMIOC: Improving diagnostics and making some progress on the emulation * Revised tracing in SMIOC and SCC2698B * Improved tracing approach in r9751 * Minor progress towards working SMIOC emulation. * [R9751] Update drivers to new code patterns after rebase Rebased on latest mame, Fixed a few issues and updated the callback code patterns based on recent changes in devcb * [R9751] Improve logging, fix interrupt race Serial no longer drops output characters * [R9751] Working on SMIOC emulation Improved SMIOC emulation accuracy, Made some progress in getting through the disktool initialization sequence, but we are still hitting a problem - It looks like disktool should be resetting the SMIOC board when it starts, but the mechanism for this has not been found. * [R9751] Improve tracing for system board registers * [R9751] Improve SMIOC emulation Still having some trouble with SMIOC but this seems to be an improvement. SMIOC is now waiting for a status to be read before applying a new status, and mandatory parameter read logic is in place. * [R9751] Incremental emulation improvements the SMIOC failure was understood and fixed, and a new approach to getting the hardware to bootstrap correctly was implemented - Still having some problems with it though. * [R9751] Fixed emulation issues * Disktool now boots to the console * UART receive only partly working, I don't think it's fully connected yet. * [R9751] Further progress on SMIOC emulation * Figured out the missing command parameter interface to the SMIOC board * Still blocked because the SMIOC interface to the breakout board through an onboard 8051 is not emulated and the disktool software depends on properties coming from it. * [R9751] Terminal is fully working for disktool * Improved the emulation of the 80188 to 451 connection in order to reliably set a status bit disktool depends on. * [R9751] Fix build after rebase * [R9751] Cleanup, tracing improvements * Remove second emulated terminal - SMIOC is now stable enough to run the terminal. * Remove older and unnecessary emulation/tracing code * r9751: Fix compile error and modify copyright holders
* Fix nonstandard syntax (nw) AJR2018-09-281-2/+2
|
* pc_lpt, upd765: removed MCFG macros (nw) Ivan Vangelista2018-09-281-11/+12
|
* machine/pdc.cpp: fixed MT07086 (nw) Ivan Vangelista2018-09-041-4/+4
|
* ti9x: Various MCFG removals. (nw) Michael Zapf2018-08-211-2/+4
|
* remove lots of MCFG_ (nw) Vas Crabb2018-07-171-9/+9
|
* as if millions of this pointers suddenly cried out in terror, and were ↵ Vas Crabb2018-06-081-5/+5
| | | | | | | 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
* Streamline machine configuration macros - everyone's a device edition. Vas Crabb2018-05-061-13/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-9/+11
| | | | | | | | | | | | | | | | | | | | | * 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-17/+19
|
* API change: Memory maps are now methods of the owner class [O. Galibert] Olivier Galibert2018-02-121-2/+2
| | | | | 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-2/+2
|
* API Change: Machine configs are now a method of the owner class, and the ↵ Olivier Galibert2018-01-171-1/+1
| | | | | | | | | | 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.
* Remove a bunch of space.device().safe_pc() from devices (nw) Olivier Galibert2017-12-301-7/+7
|
* some more device_add_mconfig. Only devices/bus remains. (nw) Ivan Vangelista2017-06-021-12/+2
|
* Goodbye MACHINE_CONFIG_FRAGMENT, it was nice knowing you. Vas Crabb2017-05-221-1/+1
| | | | | | | | | (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.
* Move static data out of devices into the device types. This is a ↵ Vas Crabb2017-05-141-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Self-registering devices prep: Vas Crabb2017-02-271-1/+1
| | | | | | | | | | | | | | * Make device_creator a variable template and get rid of the ampersands * Remove screen.h and speaker.h from emu.h and add where necessary * Centralise instantiations of screen and speaker finder templates * Add/standardise #include guards in many hearers * Remove many redundant #includes * Order #includesr to help catch headers that can't be #included alone (nw) This changes #include order to be prefix, unit header if applicable then other stuff roughly in order from most dependent to least dependent library. This helps catch headers that don't #include things that they use.
* Remove emu.h from headers (nw) Olivier Galibert2017-02-111-0/+1
| | | | | | | | | | | | Per Vas' request. If the compile fails for you (i'm thinking osx and windows native debuggers here in particular), add '#include "emu.h"' as first include of the cpp files that fail. Due to our use of precompilation and forced inclusion, emu.h must be included as the very first non-comment thing we do if we want to be sure msvc compiles are identical to gcc/clang ones. Doing it directly instead of through an include increases the correctness probability by a magnitude.
* NOTICE (TYPE NAME CONSOLIDATION) Miodrag Milanovic2016-10-221-8/+8
| | | | | Use standard uint64_t, uint32_t, uint16_t or uint8_t instead of UINT64, UINT32, UINT16 or UINT8 also use standard int64_t, int32_t, int16_t or int8_t instead of INT64, INT32, INT16 or INT8
* Created a tiny_rom_entry structure for the purposes of rom_entry ↵ Nathan Woods2016-08-061-1/+1
| | | | | | | | declarations in code, and a first pass at the required core changes to unpack tiny_rom_entry structures at runtime. WARNING - I've done preliminary testing on a tiny build (pacman works), but nothing more. I know for a fact that a full compile fails
* Cleanups and version bump Miodrag Milanovic2016-07-271-1/+0
|
* r9751: Add save state support, document progress, and clean up Brandon Munger2016-06-281-0/+13
|
* r9751: Fix race condition in PDC device. Multi disk load now possible. Brandon Munger2016-05-081-19/+21
|
* NULL->nullptr, instead of DEVCB_NULL use always DEVCB_NOOP to prevent ↵ Miodrag Milanovic2016-04-241-1/+1
| | | | confusion (nw)
* reverting: Miodrag Milanovic2016-01-201-1/+1
| | | | | | | SHA-1: 1f90ceab075c4869298e963bf0a14a0aac2f1caa * tags are now strings (nw) fix start project for custom builds in Visual Studio (nw)
* tags are now strings (nw) Miodrag Milanovic2016-01-161-1/+1
| | | | fix start project for custom builds in Visual Studio (nw)
* Cleanups and version bumpmame0169 Miodrag Milanovic2015-12-301-97/+97
|
* r9751: Update PDC documentation Brandon Munger2015-12-201-1/+82
|
* r9751: Add dip switches to PDC for HDD and FDD Brandon Munger2015-12-201-18/+67
|
* r9751: Fix floppy disk access and add log defines Brandon Munger2015-12-201-56/+89
|
* r9751: PDC floppy read support Brandon Munger2015-12-201-11/+49
|
* r9751: More PDC DMA additions Brandon Munger2015-12-201-11/+29
|
* r9751: Initial DMA hookups and driver cleanup Brandon Munger2015-12-201-104/+105
|
* r9751: rename drivers to cpp Brandon Munger2015-12-201-0/+371