Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!tank!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: Problems using ACC ACP5250 under 4.3-tahoe
Message-ID: <16626@mimsy.UUCP>
Date: 30 Mar 89 04:26:27 GMT
References: <3104@ci.sei.cmu.edu>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 22

In article <3104@ci.sei.cmu.edu> pdb@sei.cmu.edu (Patrick Barron) writes:
>Has anyone successfully gotten ACC's ACP5250 driver working under
>4.3-tahoe?  ... the kernel panics when turning the ACP5250 board on ...
>... when the driver is trying to write to Unibus map registers ... the pointer
>it's using contains garbage, and it goes off and tries to poke at
>non-existent memory.

Easy:

Between 4.3BSD and 4.3-tahoe, Mike fixed the Unibus code so that it
understands having map registers at a different location from Unibus
adapter registers (if any), and to catch bugs, set the `adapter'
register address to 0xc0000000.  That one got caught.

The map registers are now at uhp->uh_mr, rather than
&uhp->uh_uba->uba_map[0].

This does not affect well-behaved vaxif drivers, as they all go
through vaxif/if_uba.c.  (The ACC drivers are not well-behaved.)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris