summaryrefslogtreecommitdiffstatshomepage
path: root/src/devices/cpu/m68000
Commit message (Collapse)AuthorAgeFilesLines
* m68kmmu: Fixed issues with Domain/OS and its installer crashing [Hans ↵ arbee2019-11-271-1/+2
| | | | | | Ostermeyer] apollo: Fixed failures in DEX DISP7C tests 170 and 210 and selftest TE [Hans Ostermeyer]
* Make many device_execute_interface functions noexcept, including the ↵ AJR2019-11-091-38/+38
| | | | | | | | "information" overrides. This also covers several time-related functions in attotime, running_machine and emu_timer. (nw) m6805: Calculate min_cycles and max_cycles once at device_start time (Nw) attotime: Add as_khz and as_mhz (nw)
* scc68070: Add more accurate cycle counts, distinguished from MC68000 and MC68010 AJR2019-10-304-2289/+2288
|
* (nw) fix MPU4 video crash, clean up a little Vas Crabb2019-10-271-0/+17
|
* Make devdelegate more like devcb for configuration. This is a Vas Crabb2019-10-262-33/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Fix Solaris 2.11 (non-Oracle) Rick V2019-08-191-2/+2
|
* m68040: Stop CINV DATA instruction from causing F-line exception AJR2019-06-272-0/+6
|
* Fix PMMU translation error that broke macii (nw) AJR2019-06-131-1/+1
|
* m68kcpu: Apply byte smearing to PMMU as well (nw) AJR2019-06-121-61/+67
|
* m68kcpu: Alternate implementation suggested by Olivier Galibert (nw) AJR2019-06-071-4/+4
|
* Accurate byte-smearing write behavior for 32-bit members of the M68K family AJR2019-06-061-3/+48
|
* srcclean (nw) Vas Crabb2019-05-262-5/+5
|
* m68000: fixed the real MMU problem Domain/OS was having; Mac still works. ↵ arbee2019-05-231-1/+1
| | | | [Hans Ostermeyer]
* Revert ac0d80ee which broke both Mac OS and HP-UX [R. Belmont] arbee2019-05-221-1/+1
|
* m68kcpu: Show SR; rename ISP to SSP for pre-68020 (nw) AJR2019-05-192-5/+9
| | | | m68kdasm: Fix MOVEC formatting (nw)
* scc68070: Re-add a few more inadvertently illegalized opcodes (CHK, DIVS, ↵ AJR2019-04-304-124/+125
| | | | DIVU) (nw)
* Clarify that SCC68070 RTE is more like MC68010 than MC68000 (nw) AJR2019-04-293-5/+5
|
* m68000: Read the initial SP and PC from memory after rather than during ↵ AJR2019-04-291-6/+6
| | | | machine reset time. This removes the need for many drivers to reset the CPU an extra time to load the correct vector.
* SCC68070 fixes (nw) AJR2019-04-293-924/+924
| | | | | - Add several MC68000 opcodes that were inadvertently unsupported - Change behavior of CLR with memory operand to match MC68010 and later (datasheet makes it clear that the extra read is not performed)
* m680x0: Rely on the opcode tables for cpu filtering, ban "return" from ↵ Olivier Galibert2019-04-297-17981/+16221
| | | | opcode handlers, restyle [O. Galibert]
* m680x0: Normalize type names to the short versions [O. Galibert] Olivier Galibert2019-04-299-6893/+6892
|
* m680x0: Nicer function names [O. Galibert] Olivier Galibert2019-04-293-5937/+5927
|
* m680x0: Change method pointers to state ids in the big tables [O. Galibert] Olivier Galibert2019-04-294-2087/+4011
|
* m680x0: Merge table and opcode body together [O. Galibert] Olivier Galibert2019-04-295-10263/+8587
|
* m680x0: Stop using spec_proc [O. Galibert] Olivier Galibert2019-04-291-1/+1
|
* m680x0: Rename remaining_cycles to icount in alignemnt with the rest of mame ↵ Olivier Galibert2019-04-296-407/+407
| | | | [O. Galibert]
* m680x0: Only keep the bodies in the input file [O. Galibert] Olivier Galibert2019-04-296-399/+136
|
* m680x0: gratuitously convert the generator to python [O. Galibert] Olivier Galibert2019-04-296-1453/+37194
|
* Specify a few of the unique aspects of the SCC68070 core (nw) AJR2019-04-193-10/+84
|
* m68kmmu: fix ATC entry calculation error that was crashing Domain/OS [Hans ↵ arbee2019-04-191-1/+1
| | | | | | Ostermeyer] apollo: remove deprecated debug reference [Hans Ostermeyer]
* scc68070: Merge CPU device with on-chip peripheral emulation AJR2019-04-172-11/+10
| | | | | - Add internal clock divider - Add a few crude hacks to force status bits in unemulated UART and I2C
* m68000: Make the autovector abstraction a bit less leaky (nw) AJR2019-04-142-17/+18
| | | | m68008plcc: Rename device for future use (nw)
* m68kcpu.cpp: Continuation of note (nw) AJR2019-04-051-0/+1
|
* m68kcpu.cpp: Fix vector fetch width and autovector mapping (nw) AJR2019-04-041-2/+13
|
* fidel_eag68k: disable_interrupt_mixer for feagv5 (nw) hap2019-04-051-0/+4
|
* m68k_in.cpp: Fix build (this instruction will need further fixing) (nw) AJR2019-04-041-3/+6
|
* 68000: Rework interrupt handling [O. Galibert] Olivier Galibert2019-04-052-49/+78
| | | | | | | * Implement the cpu space as an address space * Make all vectored interrupts use the cpu space * Make it possible to direct the cpu space to another space, use it for amiga (which handles it as a normal AS_PROGRAM read) * Make it possible to disable the priority muxer and get 3 lines instead, use it for cps2
* (nw) Clean up the mess on master Vas Crabb2019-03-264-38/+5
| | | | | | | | | | | | | 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-254-5/+38
| | | | | This reverts commit c24473ddff715ecec2e258a6eb38960cf8c8e98e, reversing changes made to 009cba4fb8102102168ef32870892438327f3705.
* apollo: Updates and resurrection [Hans Ostermeyer] arbee2019-03-222-1/+2
| | | | | | | - Fix typo'd constant in m68kmmu that prevented trapping user accesses to kernel space - Remove need for intrusive m68k modifications - Fix crash in 3c505 networking - Fix Domain/OS booting in Normal mode
* m68301: Remove device type (nw) AJR2019-03-222-37/+0
|
* Add this call to the non-generated file (nw) AJR2019-02-112-34848/+1
|
* No thanks to gitignore (nw) AJR2019-02-111-0/+34848
|
* m68000: Add overrideable method to signal RESET instruction to internal ↵ AJR2019-02-111-0/+2
| | | | peripherals (nw)
* m68kfpu: add (d16,An) addr mode to WRITE_EA_FPE() Sven Schnelle2018-12-021-0/+7
| | | | required by netbsd ps command, which utilizes the FPU.
* m68kmmu: fix build Sven Schnelle2018-12-011-11/+0
| | | | | ps == 8 should be ps - 8, which cause a compiler error. However, the code doesn't work. It wasn't noticed due to the typo, so remove it for now.
* srcclean and fixup (nw) Vas Crabb2018-11-251-1/+1
|
* Merge pull request #4264 from hp9k/go_privilege ajrhacker2018-11-101-0/+15
|\ | | | | debugger: add 'gp' command
| * debugger: add 'gp' command Sven Schnelle2018-11-061-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | gp 'go privilege' starts execution until the privilege mode changes. This can be used to break on task switches. I.e on m68k, one could do: gp { ~sr & 0x2000 && crp_aptr == 0x1234567 } which would execute until the privilege mode changes to user mode and the CPU root pointer is 0x1234567. for cpu code, all that is needed to make this work is calling debugger_privilege_hook() when the execution level changes.
* | Merge pull request #4247 from hp9k/pflush_fc_ea R. Belmont2018-11-061-9/+51
|\ \ | | | | | | m68kmmu: support flushing ATC by FC/EA (nw)