From owner-freebsd-current Wed Nov 8 9:37:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id B391637B4C5; Wed, 8 Nov 2000 09:37:34 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eA8HbSa72451; Wed, 8 Nov 2000 10:37:29 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200011081737.eA8HbSa72451@aslan.scsiguy.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Matthew N. Dodd" Cc: Bill Paul , Warner Losh , current@FreeBSD.ORG Subject: Re: vx driver patch In-Reply-To: Your message of "Wed, 08 Nov 2000 12:15:16 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Nov 2000 10:37:28 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Wed, 8 Nov 2000, Justin T. Gibbs wrote: >> So the EISA attachment doesn't set RF_SHAREABLE if the system is using >> a level sensitive interrupt? > >The current EISA code isn't as smart as it should be. Speaking of that, I'd like to see the EISA code move to be more like PCI. We should see if there is something at slot 0 and only then attempt to probe for sub-devices on the bus. The only reason this isn't done is because I, due to the fledgling nature of the EISA code and the ahc VL card's almost looking like EISA cards, did the wrong thing here. We also need to be verifying that io ranges required to probe for slots are not already claimed by other devices before we blindly access them. For this to all work with the VL ahc cards, the EISA code will have to release all resources associated with empty slots and the ahc driver will have to grow an ISA front end. I'm willing to help out on this work (still have a functional EISA machine), but I stopped short last time over concern on how to support Alpha/PA-RISC machines that might have multiple EISA busses. >I've got uncommitted code that ties it to the ELCR. Is this stuff documented anywhere? I've always wanted to gain access to the aic7xxx card's nonvolatile region in the ELCR, but I could never find out how to do this. >Bus front end code shouldn't have to know about level/edge triggered IRQs. So long as the ELCR is guaranteed to work. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message