In message: <20020105232557.S706-100000@nihil> Michael Reifenberger <[EMAIL PROTECTED]> writes: : But why? : Where is PCI_ENABLE_IO_MODES different from: : : pci_enable_busmaster(dev); : pci_enable_io(dev, SYS_RES_IOPORT); : pci_enable_io(dev, SYS_RES_MEMORY); : : or : : data = pci_read_config(dev, PCIR_COMMAND, 2); : data |= (PCIM_CMD_PORTEN | PCIM_CMD_MEMEN | PCIM_CMD_BUSMASTEREN); : pci_write_config(dev, PCIR_COMMAND, data, 2); : : which allready existed in snd_ich ?!?
I think it has to do with the caching of these values in the pci layer. The option turns them on and updates the values in the cache, while the other options do not appear to do so. : BTW: In the case of the PCIC I still get: : pcib2: <PCI-PCI bridge> at device 30.0 on pci0 : 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. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
