#20997: PCI support is broken for Danube Lantiq
---------------------+--------------------------------
  Reporter:  pgid69  |      Owner:  developers
      Type:  defect  |     Status:  new
  Priority:  high    |  Milestone:
 Component:  kernel  |    Version:  Chaos Calmer 15.05
Resolution:          |   Keywords:
---------------------+--------------------------------

Comment (by tkn...):

 There are some other tickets which may be related to Lantiq Danube PCI
 problems causing USB or Wifi problems:
 #18369 new defect
 CC r43224 / ARV752DPW22 / 2 of 3 USB ports doesn't work
 #19856
 Lantiq ARV752DPW wifi broken

 On my Easybox 802/ARV752DPW with CC the bootlog showed (and wifi does not
 work thereafter):

 {{{
 [    0.127974] PCI host bridge /fpi@10000000/pci@E105400 ranges:
 [    0.133672]  MEM 0x0000000018000000..0x0000000019ffffff
 [    0.138939]   IO 0x000000001ae00000..0x000000001affffff
 [    0.144209] pci-xway: end probe
 [    0.147354] pci-xway: Registered platform driver![    0.196887]
 usbcore: registered new interface driver usbfs
 [    0.202498] usbcore: registered new interface driver hub
 [    0.207947] usbcore: registered new device driver usb
 [    0.213519] PCI host bridge to bus 0000:00
 [    0.217562] pci_bus 0000:00: root bus resource [mem
 0x18000000-0x19ffffff]
 [    0.224486] pci_bus 0000:00: root bus resource [io  0xffffffff]
 [    0.230499] pci_bus 0000:00: root bus resource [??? 0x00000000 flags
 0x0]
 [    0.237329] pci_bus 0000:00: No busn resource found for root bus, will
 use [bus 00-ff]

 }}}

 lscpi -vvv reads:

 {{{
 00:0e.0 Network controller: Ralink corp. RT2800 802.11n PCI
         Subsystem: Ralink corp. Device 2860
         Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B- DisINTx-
         Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort-
 <TAbort- <MAbort- >SERR- <PERR- INTx-
         Interrupt: pin A routed to IRQ 135
         Region 0: Memory at 18000000 (32-bit, non-prefetchable) [size=64K]
         Region 1: Memory at <unassigned> (32-bit, non-prefetchable)
 [size=2]
         Region 2: Memory at <unassigned> (32-bit, non-prefetchable)
 [size=2]
         Region 3: Memory at <unassigned> (32-bit, non-prefetchable)
 [size=2]
         Region 4: Memory at <unassigned> (32-bit, non-prefetchable)
 [size=2]
         Region 5: Memory at <unassigned> (32-bit, non-prefetchable)
 [size=2]
         Expansion ROM at <unassigned> [disabled] [size=2]
         Capabilities: [40] Power Management version 3
                 Flags: PMEClk+ DSI- D1- D2- AuxCurrent=375mA
 PME(D0+,D1-,D2-,D3hot+,D3cold+)
                 Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
 }}}

 Would be great for the others, if this could be fixed in trunk.
 I can not test it, because the Easybox is in active use now with BB (PCI
 works there for me).

 May be some code now checks IO_SPACE_LIMIT. The "#define "IO_SPACE_LIMIT
 0xffff" is the same in BB, kernel version 3.10.49.

--
Ticket URL: <https://dev.openwrt.org/ticket/20997#comment:1>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets

Reply via email to