summaryrefslogtreecommitdiffstatshomepage
path: root/src/devices/bus/s100
Commit message (Collapse)AuthorAgeFilesLines
* floppies: Turn the format arrays into function calls. Create a default ↵ Olivier Galibert2021-03-023-6/+6
| | | | "mfm", "fm" and "pc" list of formats. Their contents, and which driver uses what, may need some tuning.
* rs232: HLE updates AJR2021-01-261-1/+0
| | | | | | | - Remove option to change the number of start bits (1 was always the default, and the RS232 protocol requires one start bit) - Add many historically significant baud rates ranging from 50 to 7200 * ccs2810.cpp, sb8085.cpp: Update notes
* emumem: Simplify memory management. [O. Galibert] Olivier Galibert2020-11-024-8/+4
| | | | | | | | | | | | | | | | | | | | 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
* Cleaned up bitmap API. Vas Crabb2020-09-272-23/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>.
* s100/dj2db: Add UART (not fully hooked up yet); more accurate FDC reset (nw) AJR2020-03-152-10/+14
|
* Replace old MC2661 device with new SCN2651/SCN2661/SCN2641 devices and make ↵ AJR2020-03-061-30/+30
| | | | | | | | | | some associated changes - dual68: Fix baud rate by using new SCN2661B device - teleray10: Invert polarity of DIP switches; hack CTS to always be active for now - wangpc: Hook up modem control lines so that RS232 test now passes with a loopback connector - wicat: Remove some 68K interrupt conditions that were conflicting with each other - wy100: Fix CRLF problem by using new SCN2651 device; remove some old logging messages
* Revert "8255: missed one driver (nw)" Vas Crabb2019-12-171-0/+1
| | | | | | | | | | | | | | | | This reverts commit f115aa8c665fe6b531cf344e0956ff23e7043def. Revert "8255: set default tristate to 0 (nw)" This reverts commit 716d06341dba3ab9ee883ce82abe1d4fe8202b8b. This has been shown to break bw2, and it's very likely it breaks other computers in subtle ways or in ways that are only noticeable when you use a certain peripheral. It's far too dangerous, particularly late in a development cycle and with Christmas/new year coming. You can't push a change like this without checking every use of the device. Please fix any drivers you subsequently modified to depend on the change.
* 8255: set default tristate to 0 (nw) hap2019-12-141-1/+0
|
* (nw) Fixed the build. Robbbert2019-12-071-3/+3
|
* ascsasi: Actually generate the control pulses (nw) AJR2019-12-061-0/+4
|
* New S-100 device: ASC Associates SASI Host Computer Adapter [AJR, Bitsavers] AJR2019-12-062-0/+380
|
* Spring cleaning: Vas Crabb2019-11-012-6/+17
| | | | | | | | | | | | * Changed emu_fatalerror to use util::string_format semantics * Fixed some incorrectly marked up stuff in build scripts * Make internal layout compression type a scoped enum (only zlib is supported still, but at least the values aren't magic numbers now) * Fixed memory leaks in Xbox USB * There can only be one "perfect quantum" device - enforce that only the root machine can set it, as allowing subdevices to will cause weird issues with slot cards overiding it * Allow multiple devices to set maximum quantum and use the most restrictive one (it's maximum quantum, it would be minimum interleave) * Got rid of device_slot_card_interface as it wasn't providing value * Added a helper template to reduce certain kinds of boilerplate in slots/buses * Cleaned up some particularly bad slot code (plenty more of that to do), and made some slots more idiomatic
* polyfdc: Use A3, not A11 (nw) AJR2019-10-041-2/+2
|
* polyfdc: Update notes (nw) AJR2019-10-041-21/+38
|
* (nw) please try to ensure #include guards will trip special-casing in dumb ↵ Vas Crabb2019-09-161-1/+1
| | | | preprocessors to reduce filesystem operations
* s100_am310: Fix address shift (nw) AJR2019-08-281-2/+2
|
* Add dump and emulation of Alpha Micro AM-310 Communications Controller [AJR, ↵ AJR2019-08-282-0/+396
| | | | Bitsavers]
* dg640: Add base address select switch and screen raw parameters; improve ↵ AJR2019-07-212-10/+60
| | | | documentation (nw)
* (nw) split binbug into 3 sources. Robbbert2019-07-222-0/+219
|
* poly88, poly8813: Add PolyMorphic 16K RAM card and make one the default AJR2019-07-192-0/+155
|
* polyvti: Add status port (nw) AJR2019-07-181-1/+15
|
* i8212: Simplify read/write handlers (nw) AJR2019-07-181-2/+2
| | | | supstarf.cpp: Code cleanup (nw)
* poly88, poly8813: Bus expansion AJR2019-07-185-0/+474
| | | | | | - Replace additional driver RAM with S-100 bus - Convert Video Terminal Interface into a S-100 bus device - Add skeleton S-100 bus device for SSSD disk controller
* devices/machine/ins8250.cpp : Simplify handlers, Use shorter type values cam9002019-03-301-6/+6
|
* (nw) Clean up the mess on master Vas Crabb2019-03-2615-143/+88
| | | | | | | | | | | | | 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-2515-88/+143
| | | | | This reverts commit c24473ddff715ecec2e258a6eb38960cf8c8e98e, reversing changes made to 009cba4fb8102102168ef32870892438327f3705.
* bus/s100, bus/vidbrain: Eliminate address_space arguments from handlers (nw) AJR2019-02-2515-48/+48
|
* -devices/bus/kc, nasbus, s100: Removed MCFG macros, nw mooglyguy2019-02-031-79/+26
| | | | | | -devices/bus/kc/d002: Removed MACHINE_CONFIG macro, nw -drivers/horizon, kc, mpz80, nascom1, tek405x, vixen, xor100, zorba: Removed MACHINE_CONFIG macros, nw
* bus/epson_sio, bus/s100: Clean up some MCFGs (nw) AJR2019-01-184-16/+14
|
* Include floppy.h explicitly in drivers and bus cards, rather than indirectly ↵ AJR2018-11-251-0/+1
| | | | through popular FDC headers (nw)
* Identify this brick (nw) AJR2018-11-251-1/+1
|
* s100_djdma: Add a healthy amount of stub handlers to this skeleton device (nw) AJR2018-11-252-16/+265
|
* bus/s100: Collect data reads by ANDing with FF, not ORing with 0 (nw) AJR2018-11-258-16/+16
|
* machine/pic8259.h: removed MCFG macros (nw) Ivan Vangelista2018-10-311-8/+9
|
* bus/rs232.cpp: completed removal of MCFG macros (nw) Ivan Vangelista2018-10-231-21/+21
|
* upd1990a, upd4701, upd4992, upd7002: removed MCFG macros (nw) Ivan Vangelista2018-09-261-1/+2
|
* space, space, space, space, space, space, space, space, mem_mask (nw) smf-2018-09-231-2/+2
|
* wd_fdc: removed MCFG macros (nw) Ivan Vangelista2018-09-061-9/+10
|
* -in8250: De-MCFG, nw mooglyguy2018-09-041-32/+32
|
* wd_fdc: Simplify API. Plus some collateral damage [O. Galibert] Olivier Galibert2018-08-101-2/+2
|
* remove more MCFG_ (nw) Vas Crabb2018-07-071-2/+2
|
* devcb3 Vas Crabb2018-07-072-18/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Allow passing std::unique_ptr<TYPE> directly to save_pointer and remove ↵ AJR2018-06-241-1/+1
| | | | now-superfluous .get() in many drivers/devices (nw)
* wd_fdc family, msm5832: Eliminate customized MCFG_XXX_ADD macros (nw) AJR2018-05-271-2/+2
|
* Streamline machine configuration macros - everyone's a device edition. Vas Crabb2018-05-063-41/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-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.
* Sarayan made me do it. Vas Crabb2018-04-282-5/+9
| | | | | | | | | | Concrete device types now have a call operator that instantiates a device. This change means you *must* use DECLARE_DEVICE_TYPE to declare the public interface of your device, even if it's device_t. If you want to use private implementation classes, use DEFINE_DEVICE_TYPE_PRIVATE and instantiate the object finders.
* Address maps macros removal, pass 1 [O. Galibert] Olivier Galibert2018-03-141-5/+7
|
* destaticify initializations (nw) (#3289) wilbertpol2018-03-041-34/+34
| | | | | | * destaticify initializations (nw) * fix this->set_screen (nw)
* devices/bus: made some methods private now that it's possible (nw) Ivan Vangelista2018-02-141-2/+4
|