Modify

Opened 7 years ago

Closed 7 years ago

Last modified 4 years ago

#9264 closed defect (wontfix)

handle of pci I/O for ar71xx

Reported by: Ciusss89 <ciusss@…> Owned by: developers
Priority: high Milestone: Barrier Breaker 14.07
Component: kernel Version: Trunk
Keywords: I/O for ar71xx Cc:

Description

Hi all

There are noted all problem that ar71xx architecture has with pci i/o. There are many ticket on this problem. In last revision, there are update about i/o of ar71xx.

Errors of 3 week ago
My ticket

...and from dmesg snapshot yesterday

pci 0000:00:13.0: BAR 1: assigned [mem 0x10000000-0x1001ffff]
pci 0000:00:13.0: BAR 1: set to [mem 0x10000000-0x1001ffff] (PCI address [0x10000000-0x1001ffff])
pci 0000:00:11.0: BAR 5: assigned [mem 0x10020000-0x10023fff]
pci 0000:00:11.0: BAR 5: set to [mem 0x10020000-0x10023fff] (PCI address [0x10020000-0x10023fff])
pci 0000:00:11.0: BAR 6: assigned [mem 0x10024000-0x10027fff pref]
pci 0000:00:13.0: BAR 0: assigned [mem 0x10028000-0x10029fff]
pci 0000:00:13.0: BAR 0: set to [mem 0x10028000-0x10029fff] (PCI address [0x10028000-0x10029fff])
pci 0000:00:11.0: BAR 4: can't assign io (size 0x10)
pci 0000:00:11.0: BAR 0: can't assign io (size 0x8)
pci 0000:00:11.0: BAR 2: can't assign io (size 0x8)
pci 0000:00:11.0: BAR 1: can't assign io (size 0x4)
pci 0000:00:11.0: BAR 3: can't assign io (size 0x4)
PCI: mapping irq 72 to pin1@0000:00:11.0

Errors message are differents, this is forward step or back down step?

can be possible assigned at a71xx developer this problem? i can give my help?

Best regards.

Attachments (2)

dmesg (13.1 KB) - added by dk_giuse <dk_giuse89@…> 7 years ago.
dmesg.2 (13.1 KB) - added by dk_giuse <dk_giuse89@…> 7 years ago.
dmesg log

Download all attachments as: .zip

Change History (11)

comment:1 Changed 7 years ago by acoul

  • Resolution set to duplicate
  • Status changed from new to closed

Please provide more information such as pci card, openwrt firmware revision etc. about the issue you are having on your original ticket. Also do include there any similar tickets and/or other relative references to this problem.

Changed 7 years ago by dk_giuse <dk_giuse89@…>

Changed 7 years ago by dk_giuse <dk_giuse89@…>

dmesg log

comment:2 Changed 7 years ago by dk_giuse <dk_giuse89@…>

  • Resolution duplicate deleted
  • Status changed from closed to reopened

Hi,

Actually use debwrt, this should not be a problem since, debwrt use the openwrt kernel, but if you want i can install openwrt.

On rs-pro i have 3 mini-pci, 2 used:
1) Mini-pci wireless Texas Instruments ACX 111.
2) Mini-pci storage module use Promise PDC20269 IDE controller.
Interesting link about it 1 [wget http://www.atlantis.com.ua/rpstr/catalog/mini%20pci%20modules.pdf / 2]

About lspci:

root@debwrt:~# lspci 
00:00.0 Non-VGA unclassified device: Device 0700:1107 (rev 01)
00:11.0 Mass storage controller: Promise Technology, Inc. 20269 (rev 02)
00:13.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface
root@debwrt:~#


Pci resource:

root@debwrt:~# cat /sys/bus/pci/devices/0000\:00\:11.0/resource
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000010020000 0x0000000010023fff 0x0000000000040200
0x0000000010024000 0x0000000010027fff 0x000000000004e200
root@debwrt:~# cat /sys/bus/pci/devices/0000\:00\:11.0/irq 
72
root@debwrt:~# cat /sys/bus/pci/devices/0000\:00\:11.0/class
0x018085
root@debwrt:~# cat /sys/bus/pci/devices/0000\:00\:11.0/consistent_dma_mask_bits
32
root@debwrt:~# cat /sys/bus/pci/devices/0000\:00\:11.0/modalias 
pci:v0000105Ad00004D69sv0000105Asd00004D68bc01sc80i85
root@debwrt:~# cat /sys/bus/pci/devices/0000\:00\:11.0/uevent 
PCI_CLASS=18085
PCI_ID=105A:4D69
PCI_SUBSYS_ID=105A:4D68
PCI_SLOT_NAME=0000:00:11.0
MODALIAS=pci:v0000105Ad00004D69sv0000105Asd00004D68bc01sc80i85
root@debwrt:~# cat /sys/bus/pci/devices/0000\:00\:13.0/resource
0x0000000010028000 0x0000000010029fff 0x0000000000040200
0x0000000010000000 0x000000001001ffff 0x0000000000040200
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
root@debwrt:~# cat /sys/bus/pci/devices/0000\:00\:13.0/irq 
74
root@debwrt:~# cat /sys/bus/pci/devices/0000\:00\:13.0/class                
0x028000
root@debwrt:~# cat /sys/bus/pci/devices/0000\:00\:13.0/consistent_dma_mask_bits 
32
root@debwrt:~# cat /sys/bus/pci/devices/0000\:00\:13.0/modalias 
pci:v0000104Cd00009066sv0000104Csd00009067bc02sc80i00
root@debwrt:~# cat /sys/bus/pci/devices/0000\:00\:13.0/uevent   
PCI_CLASS=28000
PCI_ID=104C:9066
PCI_SUBSYS_ID=104C:9067
PCI_SLOT_NAME=0000:00:13.0
MODALIAS=pci:v0000104Cd00009066sv0000104Csd00009067bc02sc80i00
root@debwrt:~# 

Interesting line in dmesg (ssee attached file for complete output)

pci 0000:00:00.0: [0700:1107] type 0 class 0x000000
pci 0000:00:00.0: reg 10: [mem 0x00000000-0x0fffffff pref]
pci 0000:00:00.0: reg 14: [io  0x0000-0x00ff]
pci 0000:00:00.0: supports D1 D2
pci 0000:00:00.0: PME# supported from D0 D1 D2 D3hot
pci 0000:00:00.0: PME# disabled
pci 0000:00:11.0: [105a:4d69] type 0 class 0x000180
pci 0000:00:11.0: reg 10: [io  0x01f0-0x01f7]
pci 0000:00:11.0: reg 14: [io  0x03f4-0x03f7]
pci 0000:00:11.0: reg 18: [io  0x0170-0x0177]
pci 0000:00:11.0: reg 1c: [io  0x0374-0x0377]
pci 0000:00:11.0: reg 20: [io  0x6800-0x680f]
pci 0000:00:11.0: reg 24: [mem 0x00000000-0x00003fff]
pci 0000:00:11.0: reg 30: [mem 0x000dc000-0x000dffff pref]
pci 0000:00:11.0: supports D1
pci 0000:00:13.0: [104c:9066] type 0 class 0x000280
pci 0000:00:13.0: reg 10: [mem 0x00000000-0x00001fff]
pci 0000:00:13.0: reg 14: [mem 0x00000000-0x0001ffff]
pci 0000:00:13.0: supports D1 D2
pci 0000:00:13.0: PME# supported from D0 D1 D2 D3hot
pci 0000:00:13.0: PME# disabled
pci 0000:00:13.0: BAR 1: assigned [mem 0x10000000-0x1001ffff]
pci 0000:00:13.0: BAR 1: set to [mem 0x10000000-0x1001ffff] (PCI address [0x10000000-0x1001ffff])
pci 0000:00:11.0: BAR 5: assigned [mem 0x10020000-0x10023fff]
pci 0000:00:11.0: BAR 5: set to [mem 0x10020000-0x10023fff] (PCI address [0x10020000-0x10023fff])
pci 0000:00:11.0: BAR 6: assigned [mem 0x10024000-0x10027fff pref]
pci 0000:00:13.0: BAR 0: assigned [mem 0x10028000-0x10029fff]
pci 0000:00:13.0: BAR 0: set to [mem 0x10028000-0x10029fff] (PCI address [0x10028000-0x10029fff])
pci 0000:00:11.0: BAR 4: can't assign io (size 0x10)
pci 0000:00:11.0: BAR 0: can't assign io (size 0x8)
pci 0000:00:11.0: BAR 2: can't assign io (size 0x8)
pci 0000:00:11.0: BAR 1: can't assign io (size 0x4)
pci 0000:00:11.0: BAR 3: can't assign io (size 0x4)
PCI: mapping irq 72 to pin1@0000:00:11.0
PCI: mapping irq 74 to pin1@0000:00:13.0

If you want i can add your id_rsa.pub keys for give you full controll of my rs-pro.

Best regards. thanks.

comment:3 Changed 7 years ago by dk_giuse <dk_giuse89@…>

i forgot this:
Debwrt (with our Openwrt kernel) was compiled yesterday. On Openwrt, dmesg output given the same error.

root@debwrt:~# uname -a
Linux debwrt 2.6.37.6 #6 Mon Apr 18 22:47:46 CEST 2011 mips GNU/Linux
root@debwrt:~# 

Note: Nickname Ciusss89 and dk_giuse889 indicate the same person.

comment:4 Changed 7 years ago by nbd

  • Resolution set to wontfix
  • Status changed from reopened to closed

I believe the hardware is not capable of using legacy I/O resources (at least I don't know of any documented way to do so).
Please don't reopen this ticket.

comment:5 Changed 7 years ago by ciusss89 <ciusss@…>

  • Resolution wontfix deleted
  • Status changed from closed to reopened

This must be definite from two ar71xx developer [ juhosg and Kaloz ]. / Architecture developers

Why close this ticket, there are several user with the same problem, ubiquiti or anyone can be make anything for upgrade of this problem..

If this ticket is unnecessary, it was to be closed several days ago from kaloz or juhosg ...

comment:6 Changed 7 years ago by nbd

  • Resolution set to wontfix
  • Status changed from reopened to closed

kaloz and juhosg probably don't have time to look into this. I have access to all the documentation related to this, as well as reference source code and there is no indication that there is a memory range that supports PCI IO ports.

comment:7 Changed 7 years ago by anonymous

Separate IO addresspace memory is some sort of x86 legacy crap. MIPS does not have any notion of "IO ports addresspace" at all as all this stuff is quite specific to x86 legacy.

comment:8 Changed 7 years ago by ciusss89 <ciusss@…>

About error of bar_assgnment BAR_ASSIGNMENT

comment:9 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.