From owner-freebsd-arch@FreeBSD.ORG Fri Jan 2 11:24:25 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDEF216A4CE for ; Fri, 2 Jan 2004 11:24:25 -0800 (PST) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 178A643D1D for ; Fri, 2 Jan 2004 11:24:08 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 24319 invoked from network); 2 Jan 2004 19:24:07 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 2 Jan 2004 19:24:07 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i02JO3M0003210; Fri, 2 Jan 2004 14:24:04 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040102.113153.90116271.imp@bsdimp.com> Date: Fri, 02 Jan 2004 14:24:05 -0500 (EST) From: John Baldwin To: "M. Warner Losh" X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: rosti_bsd@yahoo.com cc: freebsd-arch@FreeBSD.org Subject: Re: IRQ 2 problem X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jan 2004 19:24:26 -0000 On 02-Jan-2004 M. Warner Losh wrote: > In message: > John Baldwin writes: >: On 02-Jan-2004 M. Warner Losh wrote: >: > In message: >: > John Baldwin writes: >: >: > It looks like IRQ2 isn't registered as an interrupt source, so when we >: >: > create the resource map, it looks like we skip it and shouldn't be >: >: > handing it out... >: >: >: >: Yes, it doesn't exist as a valid IRQ in the irq map anymore. Oh, but you >: >: know what, the resource manager is really buggy in this respect. For example, >: >: on my system here: >: >: >: >: Interrupt request lines: >: >: 0x0 (root0) >: >: 0x1 (atkbd0) >: >: 0x2 (root0) >: >: 0x3 (sio1) >: >: 0x4 (sio0) >: >: 0x5-0x8 (root0) >: >: 0x9 (acpi0) >: >: 0xa-0xb (root0) >: >: 0xc (psm0) >: >: 0xd (npx0) >: >: 0xe (ata0) >: >: 0xf (ata1) >: >: 0x10 (uhci0) >: >: 0x11 (sis0) >: >: 0x12 (uhci2) >: >: 0x13 (uhci1) >: >: 0x14 (fxp0) >: >: 0x15-0x17 (root0) >: >: >: >: Note that the nexus didn't add IRQ 2 as a possible resource, but the >: >: resource manager went ahead and added it anyway when the adjacent >: >: regions were added. Someone should fix the resource manager code >: >: perhaps. >: > >: > Interesting. Of course the default behavior for the devinfo stuff is >: > to say that root owns it, so I'm not 100% convinced that it is a bug >: > in the resource manager, necessarily... It fails to report shared >: > resources correctly, but they are none-the-less allocated correctly. >: > >: > I'm curious why the new PIC driver doesn't allocate IRQ 2 itself... >: >: It does it by not making it available in the first place. > > I'd have expected it to be more like: > > Interrupt request lines: > ... > 0x2 (atpic0) > ... No, I mean it shouldn't exist. It should be: 0x0 (root0) (this is a bug cause clk isn't new-bussed) 0x1 (atkbd0) 0x3 (sio1) ... -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/