Date: Sat, 13 Jan 1996 01:23:30 +1100 From: Bruce Evans <bde@zeta.org.au> To: bde@zeta.org.au, gibbs@freefall.freebsd.org Cc: freebsd-hackers@FreeBSD.org, hasty@rah.star-gate.com, neil@synthcom.com, smpatel@wam.umd.edu, terry@lambert.org Subject: Re: PnP problem... Message-ID: <199601121423.BAA09157@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>>Hmm. How do the ISA probes avoid rediscovering PCI/EISA devices? What >>happens if there is a "bt0 at isa?" (as specified in the config) on the >>ISA bus and another one on the PCI/EISA bus? I think this doesn't work >>now. >The only driver I know of that had this problem (the bt driver) handles >it by keeping a static array of ioaddrs/found information and will not >reprobe any conflicts. This should be moved to the configuration manager >(as the XXX comments in bt.c say) as there are other adapters like the >3c509 that fall into this category. I see. This depends on the PCI/EISA driver knowing something unique about the ISA device, or vice versa. You use the ISA iobase. Are there any standards at all for encoding ISA addresses in multi-mode hardware? BTW, all the ISA SCSI drivers still have an evil way of keeping track of the unit number. `xx_unit++' breaks multiple probing. >>>3) Probe all ISA devices. A probe returns whatever information can >>>be obtained non-invasively. ... >> >>That's almost no information. :-( >Depends on the card. >Most cards I've used have at most 5 different port addresses a user >can set. Some probes are non-invasive (only do reads), and these probes Some reads are invasive. Depends on the card :-). `the card' is the one that happens to be read from, not the one being probed for, so you can't guarantee not to hurt it. This is probably not a problem in practice. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601121423.BAA09157>