Re: cardbus help
: As a workaround for you, though, try adjusting the memory that the driver : requests for the register window to be based at 0xf400. Actually, for most people, just ignoring the error is enough to make it work. This bothers me. Are bridges ignoring their mapping registers? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cardbus help
In message [EMAIL PROTECTED] Mike Smith writes: : : As a workaround for you, though, try adjusting the memory that the driver : : requests for the register window to be based at 0xf400. : : Actually, for most people, just ignoring the error is enough to make : it work. : : This bothers me. Are bridges ignoring their mapping registers? It would appaer that they are. It hurts my brain that it works. But on my Inspiron, I have a dmesg of: pcic0: TI PCI-4451 PCI-CardBus Bridge irq 11 at device 15.0 on pci2 pcic0: PCI Memory allocated: 0x4400 but the bridge that this is behind claims to only decode 0xf400 and higher. I don't claim to understand... However, I think the point is moot because in current I've fixed it to clip the ranges properly. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cardbus help
: : requests for the register window to be based at 0xf400. : : Actually, for most people, just ignoring the error is enough to make : it work. : : This bothers me. Are bridges ignoring their mapping registers? It would appaer that they are. It hurts my brain that it works. I don't mind it hurting my brain; it bothers me because if we try to toe the correctness line and nobody else (including the hardware) does, then we might find ourselves stuck in a corner we can't easily get out of in a hurry. However, I think the point is moot because in current I've fixed it to clip the ranges properly. That's definitely what I intended. I guess I should fix the typos in that file too, eh? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cardbus help
In message [EMAIL PROTECTED] Mike Smith writes: : However, I think the point is moot because in current I've fixed it to : clip the ranges properly. : : That's definitely what I intended. I guess I should fix the typos in : that file too, eh? Yes. Were they mine or yours :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cardbus help
Warner Losh wrote: In message [EMAIL PROTECTED] John McCullough writes: : pcib2: routed slot 15 INTA to irq 255 : pccbb: Unable to map IRQ... : panic: resouce_list_release:can't find resource : Debugger(panic) This is a bug in pcibus issue. IRQ 255 should be treated as unallocated, so please route. As I'm still learning, I hope my questions aren't too annoying, to do this would I have the kernel route to a different IRQ (say 10) instead of 255 by default? thanks, Johnm To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cardbus help
In message [EMAIL PROTECTED] John McCullough writes: : pcib2: routed slot 15 INTA to irq 255 : pccbb: Unable to map IRQ... : panic: resouce_list_release:can't find resource : Debugger(panic) This is a bug in pcibus issue. IRQ 255 should be treated as unallocated, so please route. : Is this also an issue with pci_pci assigning resouces properly? Also : where might I find information on pci-cardbus behavior if I do find : time to tinker with the code? I'd try the pcmcia standard, the pci standard or the mindshare books. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
cardbus help
I'd like to get card bus working, however under 5.0-current my pcmcia controller is failing to load with the message: pccbb0: TI4451 PCI-CardBus Bridge at device 15.0 on pci2 pcib2: device pccbb0 requested unsupported memory randge 0x1000-0x (decoding 0xf400-0xfbff, 0xfff0-0xf) pccbb0: Could not grab register memory any insight? or will I have the pleasure of tinkering with the kerne? thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cardbus help
I'd like to get card bus working, however under 5.0-current my pcmcia controller is failing to load with the message: pccbb0: TI4451 PCI-CardBus Bridge at device 15.0 on pci2 pcib2: device pccbb0 requested unsupported memory randge 0x1000-0x (decoding 0xf400-0xfbff, 0xfff0-0xf) pccbb0: Could not grab register memory any insight? or will I have the pleasure of tinkering with the kerne? This is a bug in the way that the pccbb code allocates the register window when it hasn't been set up. The real fix actually requires the PCI code to configure the cardbus controller, but we don't do that yet (we desperately need to, though). As a workaround for you, though, try adjusting the memory that the driver requests for the register window to be based at 0xf400. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cardbus help
In message [EMAIL PROTECTED] John McCullough writes: : I'd like to get card bus working, however under 5.0-current my pcmcia : controller is failing to load with the message: : : pccbb0: TI4451 PCI-CardBus Bridge at device 15.0 on pci2 : pcib2: device pccbb0 requested unsupported memory randge : 0x1000-0x (decoding 0xf400-0xfbff, 0xfff0-0xf) : pccbb0: Could not grab register memory : : any insight? or will I have the pleasure of tinkering with the kerne? options PCI_ALLOW_UNSUPPORTED_IO_RANGE Or fix src/sys/dev/pci/pci_pci.c to properly trim the range. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cardbus help
In message [EMAIL PROTECTED] Mike Smith writes: : This is a bug in the way that the pccbb code allocates the register : window when it hasn't been set up. The real fix actually requires the : PCI code to configure the cardbus controller, but we don't do that yet : (we desperately need to, though). s/cardbus controller/any device that needs memory and/or I/O addresses assigned/. : As a workaround for you, though, try adjusting the memory that the driver : requests for the register window to be based at 0xf400. Actually, for most people, just ignoring the error is enough to make it work. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cardbus help
Warner Losh wrote: In message [EMAIL PROTECTED] John McCullough writes: : I'd like to get card bus working, however under 5.0-current my pcmcia : controller is failing to load with the message: : : pccbb0: TI4451 PCI-CardBus Bridge at device 15.0 on pci2 : pcib2: device pccbb0 requested unsupported memory randge : 0x1000-0x (decoding 0xf400-0xfbff, 0xfff0-0xf) : pccbb0: Could not grab register memory : : any insight? or will I have the pleasure of tinkering with the kerne? options PCI_ALLOW_UNSUPPORTED_IO_RANGE Or fix src/sys/dev/pci/pci_pci.c to properly trim the range. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message although config wouldn't allow the: options PCI_ALLOW_UNSUPPORTED_IO_RANGE I put it in the COPTS and it compiled alright, but now its having problems mapping irqs pcib2: routed slot 15 INTA to irq 255 pccbb: Unable to map IRQ... panic: resouce_list_release:can't find resource Debugger(panic) ... Is this also an issue with pci_pci assigning resouces properly? Also where might I find information on pci-cardbus behavior if I do find time to tinker with the code? thanks -johnm To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
