From owner-freebsd-hardware Fri Jul 30 18:14:30 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id EF35714CD3 for ; Fri, 30 Jul 1999 18:14:28 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id VAA25265; Fri, 30 Jul 1999 21:13:13 -0400 (EDT) Date: Fri, 30 Jul 1999 21:13:13 -0400 (EDT) From: "Matthew N. Dodd" To: Nikolaus Spence Cc: "'freebsd-hardware@freebsd.org'" Subject: Re: EISA DPT raid controllers In-Reply-To: <85D42D7EE2DAD2119CD400A0C9E1004F64F650@exchange.eci.us.geac.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 30 Jul 1999, Nikolaus Spence wrote: > is there anything special I would need to do to probe an EISA DPT raid > controller at startup? There's nothing in the visual kernal config > for it except under PCI. Well... Heres the deal. The DPT EISA controllers appear to need some sort of frobbing outside of what FreeBSD does to allow their config registers to be read as specified by the EISA .cfg file that ships with them. I've been unable to find out exactly what this sequence is. So the DPT EISA driver in the system is more or less broken. However. I have a hacked up dpt_eisa.c file that gets around this. What version of FreeBSD are you running and what is the model # of your card? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message