From owner-freebsd-current@FreeBSD.ORG Mon Jan 5 15:33:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E130D16A4CE; Mon, 5 Jan 2004 15:33:53 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A258843D39; Mon, 5 Jan 2004 15:33:52 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i05NXmET042029; Mon, 5 Jan 2004 16:33:49 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 05 Jan 2004 16:33:45 -0700 (MST) Message-Id: <20040105.163345.129782176.imp@bsdimp.com> To: ticso@cicely.de, ticso@cicely12.cicely.de From: "M. Warner Losh" In-Reply-To: <20040105233138.GR17023@cicely12.cicely.de> References: <20040105231533.GQ17023@cicely12.cicely.de> <20040105.162427.30502300.imp@bsdimp.com> <20040105233138.GR17023@cicely12.cicely.de> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org cc: jhb@FreeBSD.org Subject: Re: Still IRQ routing problems with bridged devices. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2004 23:33:54 -0000 In message: <20040105233138.GR17023@cicely12.cicely.de> Bernd Walter writes: : On Mon, Jan 05, 2004 at 04:24:27PM -0700, M. Warner Losh wrote: : > In message: <20040105231533.GQ17023@cicely12.cicely.de> : > Bernd Walter writes: : > : The point is that it shouldn't take an IRQ for PCI which is configured : > : for an ISA device in device.hints. : > : > We don't do that. : : We do! : : /boot/device.hints: : hint.sio.0.irq="4" : : pci_cfgintr_virgin: using routable interrupt 4 : pci_cfgintr: 0:4 INTD routed to irq 4 Ah, I see what you are saying. That would be hard to implement. Warner