On Sun, Oct 16, 2005 at 09:02:55PM -0600, M. Warner Losh wrote: > However, it won't help you. Your problem is resource allocation. > When we allocate the memory to read the CIS, something conflicts so we > can't map the CIS there. that's why you are seeing odd things. > > I'd try setting hw.cbb.start_memory=0x5200000 and other addresses that > aren't 0x88000000. With hw.cbb.start_memory=0x520000, none of my wireless cards work; they all report "Expecting link target, got ..." With it set to 0x88000000, my Atheros based card works, but my other two don't. The Atheros reports Oct 25 21:14:13 laptop kernel: cardbus1: Non-prefetchable memory at 88000000-8800ffff Oct 25 21:14:13 laptop kernel: ath0: <Atheros 5212> mem 0x88000000-0x8800ffff irq 11 at device 0.0 on cardbus1 (and ath0 then works) The ADMtek one reports Oct 25 21:15:07 laptop kernel: cardbus1: Expecting link target, got 0x0 Oct 25 21:15:07 laptop kernel: cardbus1: Resource not specified in CIS: id=10, size=100 Oct 25 21:15:07 laptop kernel: cardbus1: Resource not specified in CIS: id=14, size=400 Oct 25 21:15:07 laptop kernel: cardbus1: Non-prefetchable memory at 88000000-880003ff Oct 25 21:15:07 laptop kernel: cbb alloc res fail Oct 25 21:15:07 laptop kernel: cardbus1: Can't get memory for IO ports Oct 25 21:15:07 laptop kernel: ndis0: <SMC2635W 11Mbps Wireless Cardbus Adapter> port 0-0xff mem 0x88000000-0x880003ff at device 0.0 on cardbus1 Oct 25 21:15:07 laptop kernel: cbb alloc res fail Oct 25 21:15:07 laptop kernel: ndis0: couldn't map iospace -edReceived on Tue Oct 25 2005 - 23:30:46 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:46 UTC