On Thu, 8 Sep 2011, John Baldwin wrote:

On Thursday, September 08, 2011 1:19:23 pm Daniel Eischen wrote:

I suspect you don't really need the pciconf -lb from before r220195
because r220195 works - ath attaches and is at the correct base
address (0x88000000).  So the commit that broke ath/cardbus must
be after r220195.

The verbose dmesg and pciconf -lb are here:

   http://people.freebsd.org/~deischen/ath/dmesg.r220195.txt
   http://people.freebsd.org/~deischen/ath/dmesg.r220195.txt

I've noticed that in the non-working kernels, pcib2/cbb0
are at address 0xf8f00000, and cbb1 is at 0xf8f01000.
When the PCI configuration space is printed (in the
verbose boot), offset 0x10 shows 0xf8f00000 and
0xf8f01000.  In the working kernel, they are at 0x8000000
and 0x80001000.  It seems like kernels post Mar 31 constrain
the cardbus address range to be within the PCI bridge
range.

Yes.  You can test if that is all that causes the problem by turning off
'NEW_PCIB' in your kernel config.

I tried a recent kernel from HEAD with nooption NEW_PCIB.
The addresses are back to pre-Mar 31, but ath still doesn't
attach, verbose dmesg here:

  http://people.freebsd.org/~deischen/ath/dmesg.fails.no_new_pcib.txt

The relevent ath messages are below.

--
DE

pcib2: requested memory range 0x88000000-0xffffffff: good
unknown: Lazy allocation of 0x10000 bytes rid 0x10 type 3 at 0x88000000
cbb0: Opening memory:
cbb0: Normal: 0x88000000-0x8800ffff
cbb0: Opening memory:
cbb0: Opening memory:
cbb0: Normal: 0x88000000-0x8800ffff
cbb0: Opening memory:
found-> vendor=0x168c, dev=0x0013, revid=0x01
        domain=0, bus=3, slot=0, func=0
        class=02-00-00, hdrtype=0x00, mfdev=0
        cmdreg=0x0002, statreg=0x0290, cachelnsz=0 (dwords)
        lattimer=0x00 (0 ns), mingnt=0x0a (2500 ns), maxlat=0x1c (7000 ns)
        intpin=a, irq=11
        powerspec 2  supports D0 D3  current D0
ath0: <Atheros 5212> mem 0x88000000-0x8800ffff irq 11 at device 0.0 on cardbus0
cbb0: Opening memory:
cbb0: Normal: 0x88000000-0x8800ffff
ar5212SetPowerModeAwake: Failed to wakeup in 40ms
ar5212SetPowerModeAwake: Failed to wakeup in 40ms
ath0: unable to attach hardware; HAL status 3
cbb0: Opening memory:
device_attach: ath0 attach returned 6

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to