Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site noao.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!petrus!scherzo!allegra!princeton!astrovax!noao!grandi
From: grandi@noao.UUCP (Steve Grandi)
Newsgroups: net.unix-wizards
Subject: Re: Help needed: 3Com Ethernet Controll
Message-ID: <456@carina.noao.UUCP>
Date: Wed, 26-Feb-86 11:56:54 EST
Article-I.D.: carina.456
Posted: Wed Feb 26 11:56:54 1986
Date-Received: Fri, 28-Feb-86 22:14:51 EST
References: <277@u-mt.UUCP> <14900042@uiucdcsb>
Reply-To: grandi@carina.UUCP (Steve Grandi)
Organization: Natl. Optical Astronomy Observatories, Tucson, AZ USA
Lines: 19
Summary: 

In article <14900042@uiucdcsb> richards@uiucdcsb.CS.UIUC.EDU writes:
>
>It looks like your configuration of the board is correct, but I suspect
>that one of your other Unibus drivers are requesting a dedicated part
>of the Unibus Map before the 3com board is initialized, preventing it
>from properly acquiring the lowest part of the Unibus address space.
>
>The Fix?  Put the "device ec0 ..." entry *before* any other unibus devices
>in your configuration file, rebuild the kernel, and try it.  Devices are
>probed and attached in the order they appear in the configuration file.
>
Unfortunately, all CONTROLLERS are probed before any DEVICES so the UDA-50/RA
driver will still get in and grab the Unibus memory first.  It is a
simple hack to autoconf.c to reverse this order so all devices get probed
first; I had to do this for one of my 750s with a UDA-50 and a 3-Com card on
the same Unibus when I switched to the RIACS UDA driver.
-- 
Steve Grandi, National Optical Astronomy Observatories, Tucson, AZ, 602-325-9228
{arizona,decvax,hao,ihnp4,seismo}!noao!grandi  grandi%draco@Hamlet.Caltech.Edu