summaryrefslogtreecommitdiffstats
path: root/etc
diff options
context:
space:
mode:
authorrgrimes <rgrimes@FreeBSD.org>1993-10-13 15:59:30 +0000
committerrgrimes <rgrimes@FreeBSD.org>1993-10-13 15:59:30 +0000
commit2b976dc12a3a9fab6a72bb13af6845cb37d447c2 (patch)
tree6e42952d40fb371144517d32adb4e0b637c4beb1 /etc
parent69995035ce3f7c91e0c1ab237ac5bc9115e0816b (diff)
downloadFreeBSD-src-2b976dc12a3a9fab6a72bb13af6845cb37d447c2.zip
FreeBSD-src-2b976dc12a3a9fab6a72bb13af6845cb37d447c2.tar.gz
ALL:
Removed patch kit headers and rcsid strings, add $Id$. isa.c: Removed old #ifdef notyet isa_configure code, since it will never be used, and I have done 90% of what it attempted to. Add conflict checking code that searchs back through the devtab's looking for any device that has already been found that may conflict with what we are about to probe. Checks are mode for I/O address, memory address, IRQ, and DRQ. This should stop the screwing up of any device that has alread been found by other device probes. Print out messages when we are not going to probe a device due to a conflict so the user knows WHY something was not found. For example: aha0 not probed due to irq conflict with ahb0 at 11 Now print out a message when a device is not found so the user knows that it was probed for, but could not be found. For example: ed1 not found at 0x320 For devices that have I/O address < 0x100 say that they are on the motherboard, not on isa! The 0x100 magic number is per ISA spec. It may seem funny that pc0 and sc0 report as being on the motherboard, but this is due to the fact that the I/O address used is that of the keyboard controller which IS on the motherboard. We really need to split the keyboard probe from the display probe. It is completly legal to build a pc with out one or the other, or even with out both! npx.c: Return -1 from the probe routine if we are using the Emulator so that the i/o addresses are not printed, this is the same trick used for 486's. Do not print the ``Errors reported via Exception 16'', and ``Errors reported via IRQ 13'' messages any more, since these just lead to more user confusion that anything. It still prints the message ``Error reporting broken, using 387 emulator'' so that the person is aware that there mother board is ill.
Diffstat (limited to 'etc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud