From owner-freebsd-current Wed Jun 2 0: 8:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id B36621529C for ; Wed, 2 Jun 1999 00:08:27 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA43830; Wed, 2 Jun 1999 08:08:44 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 2 Jun 1999 08:08:43 +0100 (BST) From: Doug Rabson To: "Matthew N. Dodd" Cc: Mark Newton , current@freebsd.org Subject: Re: IRQ sharing with newbus In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Jun 1999, Matthew N. Dodd wrote: > On Tue, 1 Jun 1999, Doug Rabson wrote: > > For EISA, it should be possible to add RF_SHAREABLE to the > > bus_alloc_resource call (assuming that EISA interrupts are shareable > > like pci interrupts). > > The observed behavior suggests that RF_SHAREABLE is not being honored. > > dpt99: DPT PM2022A/9X FW Rev. 07CK, 1 channel, 64 CCBs > dpt0: at slot 4 on eisa0 > dpt0: DPT PM2022A/9X FW Rev. 07CK, 1 channel, 64 CCBs > dpt99: DPT PM2022A/9X FW Rev. 005A, 1 channel, 64 CCBs > dpt1: at slot 5 on eisa0 > dpt1: No irq?! > device_probe_and_attach: dpt1 attach returned -1 > > (The 'dpt99' lines are an artifact of the mechanism I'm using to complete > the probe.) > > Now, since the resource ranges aren't printed anymore, you can't see that > both cards are using (set to use) the same IRQ. The EISA bus code needs a new maintainer (who could put back such things as resource reporting). Are you interested? You seem to be one of the few people who actively uses this bus. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message