From owner-freebsd-hackers Wed Aug 15 5: 2:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.utep.edu (mail.cs.utep.edu [129.108.5.3]) by hub.freebsd.org (Postfix) with ESMTP id BEBFB37B403; Wed, 15 Aug 2001 05:02:43 -0700 (PDT) (envelope-from janb@cs.utep.edu) Received: from gecko (gecko [129.108.5.51]) by cs.utep.edu (8.11.3/8.11.3) with ESMTP id f7FC2e024038; Wed, 15 Aug 2001 06:02:40 -0600 (MDT) Date: Wed, 15 Aug 2001 06:02:40 -0600 (MDT) From: X-Sender: To: Mike Smith Cc: Subject: Re: more Newbus questions In-Reply-To: <200108142302.f7EN1w403960@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > None of these are newbus items. Interrupt dispatch is not managed by > newbus (due to the costs involved). Instead, interrupts are attached > with bus_setup_intr, which forwards the interrupt handler and argument > to platform-specific code. The resource mananger is involved (since > interrupts are a managed resource), and interrupts must be allocated > using bus_alloc_resource before being set up. > Could you possibly go over how this works on the i386. Is there a global structure that keeps track of all allocated IRQs and interrupt handling routines? What I really need, is to find out, where this structure is built, so that at this point, I can instead build the structure that xmach needs. Or, alternatively, I can wait until that structure is done, and then make the xmach structure from that... Thanks again, JAn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message