From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 17:25:04 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3352E37B401 for ; Wed, 28 May 2003 17:25:04 -0700 (PDT) Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 576BF43F85 for ; Wed, 28 May 2003 17:24:56 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from foem (IDENT:chuckwebweaving.org@foem [10.11.0.2]) h4T0Otv7061684 for ; Thu, 29 May 2003 02:24:55 +0200 (CEST) (envelope-from dirkx@webweaving.org) Date: Thu, 29 May 2003 02:24:55 +0200 (CEST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@foem To: hackers@freebsd.org Message-ID: <20030529022139.Y22309-100000@foem> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Who configures the pci/pcmcia bridge X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2003 00:25:04 -0000 Even when the BIOS is instructed to assign an IRQ - boot -v shows FreeBSD 5.0-RELEASE #0: Mon Apr 28 11:24:06 CEST 2003 dirkx@foem.leiden.webweaving.org:/usr/obj/usr/src/sys/WLEIDEN.93264 ... bios32: Found BIOS32 Service Directory header at 0xc00fdb00 bios32: Entry = 0xf5f23 (c00f5f23) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf5ec0+0x2ac pnpbios: Found PnP BIOS data at 0xc00fdb10 pnpbios: Entry = f0000:5159 Rev = 1.0 pci_open(1): mode 1 addr port (0x0cf8) is 0x80000050 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71008086) pcib0: at pcibus 0 on motherboard pci0: on pcib0 pci0: physical bus=0 ... found-> vendor=0x1180, dev=0x0475, revid=0x80 bus=0, slot=17, func=0 class=06-07-00, hdrtype=0x02, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x07 (1750 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 found-> vendor=0x1180, dev=0x0475, revid=0x80 bus=0, slot=18, func=0 class=06-07-00, hdrtype=0x02, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x07 (1750 ns) intpin=a, irq=255 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 3, range 32, base fedfb000, size 12, enabled and hence: pci_cfgintr: can't route an interrupt to 0:17 INTA pcic0: at device 17.0 on pci0 pcic0: PCI Memory allocated: 0x88000000 pci_cfgintr: can't route an interrupt to 0:17 INTA pcic0: No PCI interrupt routed, trying ISA. pcic0: Polling mode ... pccard0: on pcic0 pci_cfgintr: can't route an interrupt to 0:18 INTA pcic1: at device 18.0 on pci0 pcic1: PCI Memory allocated: 0x88001000 pci_cfgintr: can't route an interrupt to 0:18 INTA pcic1: No PCI interrupt routed, trying ISA. pcic1: Polling mode Which I suspect leads tot the wi0..wi4 watchdog time outs. Now -who- should ensure that an IRQ is configured ? Is this the kernel doing something wrong, or the board ? (Ricoh RL5C475 - OEM model, no version #). Dw