From owner-freebsd-mobile@FreeBSD.ORG Tue Apr 20 09:49:21 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8B5716A4CE for ; Tue, 20 Apr 2004 09:49:21 -0700 (PDT) Received: from hexagon.stack.nl (hexagon.stack.nl [131.155.140.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8072D43D2F for ; Tue, 20 Apr 2004 09:49:21 -0700 (PDT) (envelope-from marcov@stack.nl) Received: from toad.stack.nl (zen.stack.nl [IPv6:2001:610:1108:5010::130]) by hexagon.stack.nl (Postfix) with ESMTP id 40855490#484B751E9 for ; Tue, 20 Apr 2004 18:49:20 +0200 (CEST) Received: by toad.stack.nl (Postfix, from userid 816) id 24EE2D7; Tue, 20 Apr 2004 18:49:20 +0200 (CEST) To: freebsd-mobile@freebsd.org Date: Tue, 20 Apr 2004 18:49:19 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20040420164920.24EE2D7@toad.stack.nl> From: marcov@stack.nl (Marco van de Voort) Subject: Re: unsupported io range problem X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Apr 2004 16:49:21 -0000 ----- Forwarded message (env-from marcov) ----- Subject: Re: unsupported io range problem In-Reply-To: <408519D9.3040009@rosleuchter.de> from Christoph Rosport at Apr 20, 2004 02:38:49 pm To: Christoph Rosport Date: Tue, 20 Apr 2004 18:48:34 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL88 (25)] Return-Path: Content-Length: 2374 > Marco van de Voort wrote: > my IBM R40 works fine with these settings: > > hw.pci.allhw.pci.allow_unsupported_io_range="1" > hw.cbb.memory_range="0x20000000" > > You must check the second key for your special device. Didn't help, but the problem seems to be the I/O ranges, not the memory ranges. Could it be related to the fact that these devises are attached to bus PCI1 ? Or is that normal for ACPI? [ relevant snip] xl0: <3Com 3c900-COMBO Etherlink XL> port 0xfcc0-0xfcff irq 11 at device 1.0 on pci1 end (fcff) > sc->iolimit (fff) pcib1: device xl0 requested unsupported I/O range 0xfcc0-0xfcff (decoding 0x0-0xfff) xl0: couldn't map ports/memory device_probe_and_attach: xl0 attach returned 6 atapci1: port 0xfc80-0xfc8f,0xfc98-0xfc9b,0xfca0-0xfca7,0xfcb0-0xfcb3,0xfcb8-0xfcbf irq 11 at device 5.0 on pci1 end (fc8f) > sc->iolimit (fff) pcib1: device atapci1 requested unsupported I/O range 0xfc80-0xfc8f (decoding 0x0-0xfff) atapci1: [MPSAFE] atapci1: HW has secondary channel disabled end (fcbf) > sc->iolimit (fff) pcib1: device atapci1 requested unsupported I/O range 0xfcb8-0xfcbf (decoding 0x0-0xfff) ahc0: port 0xf800-0xf8ff mem 0xfdfff000-0xfdffffff irq 11 at device 7.0 on pci1 end (f8ff) > sc->iolimit (fff) pcib1: device ahc0 requested unsupported I/O range 0xf800-0xf8ff (decoding 0x0-0xfff) ahc0: can't allocate register resources device_probe_and_attach: ahc0 attach returned 12 xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xfc40-0xfc7f irq 11 at device 8.0 on pci1 end (fc7f) > sc->iolimit (fff) pcib1: device xl0 requested unsupported I/O range 0xfc40-0xfc7f (decoding 0x0-0xfff) xl0: couldn't map ports/memory device_probe_and_attach: xl0 attach returned 6 and sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) ----- End of forwarded message (env-from marcov) -----