On Sun, 6 Jan 2002, M. Warner Losh wrote: ... > : pci2: <PCI bus> on pcib2 > : pccbb0: <RF5C478 PCI-CardBus Bridge> mem 0x50000000-0x50000fff irq 11 at device > : 0.0 on pci2 > : pcib2: device pccbb0 requested unsupported memory range 0x50000000-0x50000fff > : (decoding 0xc0200000-0xcfffffff, 0xe8000000-0xefffffff) > : pccbb0: Could not map register memory > : device_probe_and_attach: pccbb0 attach returned 12 > : pccbb0: <RF5C478 PCI-CardBus Bridge> mem 0x50100000-0x50100fff irq 11 at device > : 0.1 on pci2 > : pcib2: device pccbb0 requested unsupported memory range 0x50100000-0x50100fff > : (decoding 0xc0200000-0xcfffffff, 0xe8000000-0xefffffff) > : pccbb0: Could not map register memory > : device_probe_and_attach: pccbb0 attach returned 12 > > Maybe you need some patches to the pci bridge code to map the range > requested, or to just allow it (since it just works anyway). There's > another kludge option: PCI_ALLOW_UNSUPPORTED_IO_RANGE. Thanks for the hint. After applying my attached patch this option got accepted and led to probed and attached NEWCARD devices. Inserting a FA411 Card leads to a frozen system (after reading the CIS info) until the card gets ejected. Haven't tried the OLDCARD (which worked in compat mode anyway) yet. Maybe NEWCARD is trying to use wrong resources here...
Maybe we need some special handling for the new Intel-mobile-chipset used by IBM (which supports up to 1GB of memory). Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS
--- conf/options.orig Sat Dec 22 17:05:24 2001 +++ conf/options Mon Jan 7 02:44:51 2002 @@ -418,4 +418,5 @@ PCI_QUIET opt_pci.h PCI_ENABLE_IO_MODES opt_pci.h +PCI_ALLOW_UNSUPPORTED_IO_RANGE opt_pcib.h # NFS options --- dev/pci/pci_pci.c.orig Mon Nov 26 08:12:35 2001 +++ dev/pci/pci_pci.c Mon Jan 7 02:44:27 2002 @@ -35,4 +35,7 @@ */ +#include "opt_bus.h" +#include "opt_pcib.h" + #include <sys/param.h> #include <sys/systm.h>
