On Tue, 25 Apr 2000, Chris Tribo wrote:

>     OK, I don't think I2C should be able to cause that normally... Would

  Normally it shoudn't, but I suspect a pointer in dtop.c was probably
clobbered due to a bug in the timeout/untimeout to callout conversion.

>     Is this strictly an I2C problem and it's "safe" to use 1.4X on 3MAX+, or
> is this yet unknown ?

  I think it was just a problem with the dtop driver on the Maxine, and I
have committed a fix for it.

--
Michael L. Hitch			mhitch@montana.edu
Computer Consultant
Information Technology Center
Montana State University	Bozeman, MT	USA