Date: Wed, 15 Jan 1997 09:34:28 +0900 (JST) From: Naoki Hamada <nao@sbl.cl.nec.co.jp> To: daver@chaos.tmok.com Cc: mcgovern@spoon.beta.com, hackers@FreeBSD.ORG Subject: Re: 3com 3c509 / SB16 PNP Problems... Message-ID: <199701150034.JAA28430@sirius.sbl.cl.nec.co.jp> In-Reply-To: Dave Costantino's message of "Tue, 14 Jan 1997 18:13:43 -0500 (EST)" <199701142313.SAA02192@chaos.tmok.com> References: <199701142313.SAA02192@chaos.tmok.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dave Costantino: >Here's what I did to make it work... I don't guarantee this will work with >anyone elses configuration, but it's working for me. PnP feature of the 3C509 and newer 3C509B adapters is nothing to do with this problem. 3C509 adapters use 'id port' while initialization. Id port is the most recently accessed address among i/o port 0x100, 0x110 ... 0x1f0. Since the driver a priori assumes that the id port is 0x100 and some type of sound blaster cards use i/o port 0x100, you fail to detect your 3C509 adapter. There seems no device which use i/o port 0x110, so the exact solution is: >2) In /usr/src/sys/i386/isa/elink.h, I changed: "#define ELINK_ID_PORT 0x100" > to read "#define ELINK_ID_PORT 0x110". This must be committed. Linux way apparently seems better, but it is known that sometimes it fails. - nao
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701150034.JAA28430>