91c7d26095
Show IOSPACE doesn't always get the number of devices right due to device creativity. o The distinction between UNIT and DEVICE has blurred o MUX devices merge several physical devices into one device/unit o Dynamic device sizing has made things more volatile. This edit solves the problem for SHOW IOSPACE by adding an (optional) word to the DIBs. The word contains the amount of IO space consumed by each instance of the physical device that's being emulated. E.G., if it's a DZ11, the device is the DZ11 module, or 8 lines, even though the MUX device may support 32. This enables SHOW IOSPACE to determine the number of physical devices being emulated, which is what folks need when configuring software. The word may have other uses - in a generic dynamic device sizing routine - which is why the amount of IOSPACE per device was chosen rather than the 'number of physical devices.' The edit should not make any existing device regress. If the new word (ulnt) is zero (not initialized), SHOW IOSPACE will default to the number of units in the device, or if there's no device (CPUs), 1 as before. If it is present, the number of devices is the calculated as total allocation/allocation-per-device. The edit updates all the devices that seem to require this treatment, and all the processors that define the UNIBUS/QBUS DIBs. |
||
|---|---|---|
| .. | ||
| pdp10_bug_history.txt | ||
| pdp10_cpu.c | ||
| pdp10_defs.h | ||
| pdp10_fe.c | ||
| pdp10_ksio.c | ||
| pdp10_lp20.c | ||
| pdp10_mdfp.c | ||
| pdp10_pag.c | ||
| pdp10_rp.c | ||
| pdp10_sys.c | ||
| pdp10_tim.c | ||
| pdp10_tu.c | ||
| pdp10_xtnd.c | ||