pci_enable_device fails on MPC8541

pci_enable_device fails on MPC8541

[Bizhan Gholikhamseh (bgholikh)]

[-- Attachment #1: Type: text/plain, Size: 953 bytes --]

Hi All,
I am using two evaluation board from freescale, 8540ADS and MPC8541. The
same PCI driver is being compiled and loaded on both platforms. The same
PCI driver (developed by me) for DSP board compiled and loaded on both
platforms. 
 
When I type: "insmod C6415.ko" on 8541 board, I get the following error:
"PCI: Device 0000:02:01.0 not available because of resource collisions"
This messages is because of the execution of the generic PCI Linux
command:
"pci_enable_device(pdev)"
The same API has no problem on 8540ADS.
 
>From UBOOT I can see my device is on bus 3:
=> pci 3
Scanning PCI devices on bus 3
BusDev FUN    VendorID    DeviceID    Device Class    Sub-Class
------------------------------------------------------------------------
--------------------
03.01.00            0x104c    0xa106        .........
 
Any idea why the insmod fails on one board and not on the other one?
 
Many thanks in advance,
Bizhan

[-- Attachment #2: Type: text/html, Size: 3657 bytes --]

Re: pci_enable_device fails on MPC8541

[Kumar Gala]

Bizhan,

A few questions:

1. what kernel version are you using on these boards:
2. can you do an lspci -v on the boards

- kumar

On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\))) wrote:

> Hi All,
> I am using two evaluation board from freescale, 8540ADS and  
> MPC8541. The
> same PCI driver is being compiled and loaded on both platforms. The  
> same
> PCI driver (developed by me) for DSP board compiled and loaded on both
> platforms.
>
> When I type: "insmod C6415.ko" on 8541 board, I get the following  
> error:
> "PCI: Device 0000:02:01.0 not available because of resource  
> collisions"
> This messages is because of the execution of the generic PCI Linux
> command:
> "pci_enable_device(pdev)"
> The same API has no problem on 8540ADS.
>
>
>> From UBOOT I can see my device is on bus 3:
>>
> => pci 3
> Scanning PCI devices on bus 3
> BusDev FUN    VendorID    DeviceID    Device Class    Sub-Class
> ---------------------------------------------------------------------- 
> --
> --------------------
> 03.01.00            0x104c    0xa106        .........
>
> Any idea why the insmod fails on one board and not on the other one?
>
> Many thanks in advance,
> Bizhan
>
> <ATT2118305.txt>
>

RE: pci_enable_device fails on MPC8541

[Bizhan Gholikhamseh (bgholikh)]

Kumar,
I am using Linux 2.6.11 version. Currently I do not have
the "lspci" patch integrated into my Linux image, however the /proc/pci
exists. The Freescale FAE is telling me to turn ON bit 3 on SW1 (i.e.
making Tsi320 to transparent bridge) on the mother board (i.e. arcadia
board). After doing that, the system hangs during boot right after the
decompressing the Linux image.
=20
Regards,
Bizhan

-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@freescale.com]=20
Sent: Monday, August 08, 2005 1:34 PM
To: Bizhan Gholikhamseh (bgholikh)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: pci_enable_device fails on MPC8541

Bizhan,

A few questions:

1. what kernel version are you using on these boards:
2. can you do an lspci -v on the boards

- kumar

On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\))) wrote:

> Hi All,
> I am using two evaluation board from freescale, 8540ADS and MPC8541.=20
> The same PCI driver is being compiled and loaded on both platforms.=20
> The same PCI driver (developed by me) for DSP board compiled and=20
> loaded on both platforms.
>
> When I type: "insmod C6415.ko" on 8541 board, I get the following
> error:
> "PCI: Device 0000:02:01.0 not available because of resource=20
> collisions"
> This messages is because of the execution of the generic PCI Linux
> command:
> "pci_enable_device(pdev)"
> The same API has no problem on 8540ADS.
>
>
>> From UBOOT I can see my device is on bus 3:
>>
> =3D> pci 3
> Scanning PCI devices on bus 3
> BusDev FUN    VendorID    DeviceID    Device Class    Sub-Class
> ----------------------------------------------------------------------
> --
> --------------------
> 03.01.00            0x104c    0xa106        .........
>
> Any idea why the insmod fails on one board and not on the other one?
>
> Many thanks in advance,
> Bizhan
>
> <ATT2118305.txt>
>

RE: pci_enable_device fails on MPC8541

[Bizhan Gholikhamseh (bgholikh)]

[-- Attachment #1: Type: text/plain, Size: 1887 bytes --]

Hi Kumar,
I am using Linux 2.6.11, u-boot 1.1.2.
I see failure in pci_enable_device with message: 
"PCI: Device 0000:02:01.0 not available because of resource collisions" 

I have attached three files:
lspci_output.txt: out put of the "lspci -v"
proc_pci.txt: output of the "cat /proc/pci"
u-boot.txt: output of the "pci command at u-boot"

Any help greatly appreciated,
Bizhan
-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@freescale.com] 
Sent: Monday, August 08, 2005 1:34 PM
To: Bizhan Gholikhamseh (bgholikh)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: pci_enable_device fails on MPC8541

Bizhan,

A few questions:

1. what kernel version are you using on these boards:
2. can you do an lspci -v on the boards

- kumar

On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\))) wrote:

> Hi All,
> I am using two evaluation board from freescale, 8540ADS and MPC8541. 
> The same PCI driver is being compiled and loaded on both platforms. 
> The same PCI driver (developed by me) for DSP board compiled and 
> loaded on both platforms.
>
> When I type: "insmod C6415.ko" on 8541 board, I get the following
> error:
> "PCI: Device 0000:02:01.0 not available because of resource 
> collisions"
> This messages is because of the execution of the generic PCI Linux
> command:
> "pci_enable_device(pdev)"
> The same API has no problem on 8540ADS.
>
>
>> From UBOOT I can see my device is on bus 3:
>>
> => pci 3
> Scanning PCI devices on bus 3
> BusDev FUN    VendorID    DeviceID    Device Class    Sub-Class
> ----------------------------------------------------------------------
> --
> --------------------
> 03.01.00            0x104c    0xa106        .........
>
> Any idea why the insmod fails on one board and not on the other one?
>
> Many thanks in advance,
> Bizhan
>
> <ATT2118305.txt>
>

[-- Attachment #2: lspci_output.txt --]
[-- Type: text/plain, Size: 2227 bytes --]

# lspci -v
00:11.0 Class 0604: 10e3:0513
        Flags: bus master, 66Mhz, medium devsel, latency 128
        Memory at 9ffff000 (32-bit, non-prefetchable)
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=255
        Memory behind bridge: 9fe00000-9fefffff
        Prefetchable memory behind bridge: 000000009fd00000-000000009fd00000

00:15.0 Class 0604: 104c:ac28 (rev 02)
        Flags: bus master, medium devsel, latency 128
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=226
        Memory behind bridge: 9f000000-9fcfffff
        Prefetchable memory behind bridge: 000000009ef00000-000000009ef00000
        Secondary status: SERR

01:02.0 Class 0601: 1106:0686 (rev 40)
        Flags: bus master, stepping, medium devsel, latency 0, IRQ 98
        Capabilities: [c0] Power Management version 2

01:02.1 Class 0101: 1106:0571 (rev 06) (prog-if 8a)
        Flags: stepping, medium devsel, IRQ 98
        I/O ports at cc00
        Capabilities: [c0] Power Management version 2

01:02.2 Class 0c03: 1106:3038 (rev 1d)
        Subsystem: 0925:1234
        Flags: bus master, medium devsel, latency 128, IRQ 97
        I/O ports at ffe0
        Capabilities: [80] Power Management version 2

01:02.3 Class 0c03: 1106:3038 (rev 1d)
        Subsystem: 0925:1234
        Flags: bus master, medium devsel, latency 128, IRQ 97
        I/O ports at ffc0
        Capabilities: [80] Power Management version 2

01:02.4 Class 0000: 1106:3057 (rev 40)
        Flags: medium devsel, IRQ 98
        Capabilities: [68] Power Management version 2

01:02.5 Class 0401: 1106:3058 (rev 50)
        Flags: medium devsel, IRQ 96
        I/O ports at fe00
        I/O ports at fdfc
        I/O ports at fdf8
        Capabilities: [c0] Power Management version 2

01:02.6 Class 0780: 1106:3068 (rev 30)
        Flags: medium devsel, IRQ 96
        I/O ports at fc00
        Capabilities: [d0] Power Management version 2

02:01.0 Class 0000: 104c:a106 (rev 01)
        Flags: bus master, medium devsel, latency 128, IRQ 96
        Memory at 9f800000 (32-bit, prefetchable)
        Memory at 9f000000 (32-bit, non-prefetchable)
        I/O ports at <ignored>
        Capabilities: [40] Power Management version 2

[-- Attachment #3: proc_pci.txt --]
[-- Type: text/plain, Size: 1995 bytes --]

# cat /proc/pci
PCI devices found:
  Bus  0, device  17, function  0:
    PCI bridge: PCI device 10e3:0513 (Tundra Semiconductor Corp.) (rev 0).
      IRQ 96.
      Master Capable.  Latency=128.
      Non-prefetchable 32 bit memory at 0x9ffff000 [0x9fffffff].
  Bus  0, device  21, function  0:
    PCI bridge: Texas Instruments PCI2050 PCI-to-PCI Bridge (rev 2).
      IRQ 99.
      Master Capable.  Latency=128.  Max Lat=4.
  Bus  1, device   2, function  0:
    ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 64).
      IRQ 98.
  Bus  1, device   2, function  1:
    IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Mast.      IRQ 98.
      I/O at 0xcc00 [0xcc0f].
  Bus  1, device   2, function  2:
    USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 29).
      IRQ 97.
      Master Capable.  Latency=128.
      I/O at 0xffe0 [0xffff].
  Bus  1, device   2, function  3:
    USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2) (rev 29).
      IRQ 97.
      Master Capable.  Latency=128.
      I/O at 0xffc0 [0xffdf].
  Bus  1, device   2, function  4:
    Non-VGA unclassified device: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 6.      IRQ 98.
  Bus  1, device   2, function  5:
    Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev.      IRQ 96.
      I/O at 0xfe00 [0xfeff].
      I/O at 0xfdfc [0xfdff].
      I/O at 0xfdf8 [0xfdfb].
  Bus  1, device   2, function  6:
    Communication controller: VIA Technologies, Inc. Intel 537 [AC97 Modem] (rev 48).
      IRQ 96.
      I/O at 0xfc00 [0xfcff].
  Bus  2, device   1, function  0:
    Non-VGA unclassified device: Texas Instruments TMS320C6205 Fixed Point DSP (rev 1).
      IRQ 96.
      Master Capable.  Latency=128.
      Prefetchable 32 bit memory at 0x9f800000 [0x9fbfffff].
      Non-prefetchable 32 bit memory at 0x9f000000 [0x9f7fffff].
      I/O at 0x0 [0xf].


[-- Attachment #4: u-boot.txt --]
[-- Type: text/plain, Size: 1297 bytes --]

=> pci 3
Scanning PCI devices on bus 3
BusDevFun  VendorId   DeviceId   Device Class       Sub-Class
_____________________________________________________________
03.01.00   0x104c     0xa106     Build before PCI Rev2.0 0x00
=> pci header 03.01.00
  vendor ID =                   0x104c
  device ID =                   0xa106
  command register =            0x0007
  status register =             0x0210
  revision ID =                 0x01
  class code =                  0x00 (Build before PCI Rev2.0)
  sub class code =              0x00
  programming interface =       0x00
  cache line =                  0x08
  latency time =                0x80
  header type =                 0x00
  BIST =                        0x00
  base address 0 =              0x81000008
  base address 1 =              0x81800000
  base address 2 =              0xe2004001
  base address 3 =              0x00000000
  base address 4 =              0x00000000
  base address 5 =              0x00000000
  cardBus CIS pointer =         0x00000000
  sub system vendor ID =        0x0000
  sub system ID =               0x0000
  expansion ROM base address =  0x00000000
  interrupt line =              0x60
  interrupt pin =               0x01
  min Grant =                   0x00
  max Latency =                 0x00

Re: pci_enable_device fails on MPC8541

[Kumar Gala]

Do you need support for the VIA IDE controller?  I'm not sure if that  
is causing you issues.

Also, can you try enabling DEBUG in arch/ppc/kernel/pci.c and send a  
boot log.  I'm trying to figure out what is causing the resource  
conflict.  It appears that the memory resource is reasonable, but  
there could be possible conflict on the IO resource side.

Also, if you can send logs of the same thing from the working 8540  
ADS that would be helpful.

- kumar

On Aug 9, 2005, at 12:18 PM, Bizhan Gholikhamseh \(((bgholikh\))) wrote:

> Hi Kumar,
> I am using Linux 2.6.11, u-boot 1.1.2.
> I see failure in pci_enable_device with message:
> "PCI: Device 0000:02:01.0 not available because of resource  
> collisions"
>
> I have attached three files:
> lspci_output.txt: out put of the "lspci -v"
> proc_pci.txt: output of the "cat /proc/pci"
> u-boot.txt: output of the "pci command at u-boot"
>
> Any help greatly appreciated,
> Bizhan
> -----Original Message-----
> From: Kumar Gala [mailto:kumar.gala@freescale.com]
> Sent: Monday, August 08, 2005 1:34 PM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: pci_enable_device fails on MPC8541
>
> Bizhan,
>
> A few questions:
>
> 1. what kernel version are you using on these boards:
> 2. can you do an lspci -v on the boards
>
> - kumar
>
> On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\)))  
> wrote:
>
>
>> Hi All,
>> I am using two evaluation board from freescale, 8540ADS and MPC8541.
>> The same PCI driver is being compiled and loaded on both platforms.
>> The same PCI driver (developed by me) for DSP board compiled and
>> loaded on both platforms.
>>
>> When I type: "insmod C6415.ko" on 8541 board, I get the following
>> error:
>> "PCI: Device 0000:02:01.0 not available because of resource
>> collisions"
>> This messages is because of the execution of the generic PCI Linux
>> command:
>> "pci_enable_device(pdev)"
>> The same API has no problem on 8540ADS.
>>
>>
>>
>>> From UBOOT I can see my device is on bus 3:
>>>
>>>
>> => pci 3
>> Scanning PCI devices on bus 3
>> BusDev FUN    VendorID    DeviceID    Device Class    Sub-Class
>> --------------------------------------------------------------------- 
>> -
>> --
>> --------------------
>> 03.01.00            0x104c    0xa106        .........
>>
>> Any idea why the insmod fails on one board and not on the other one?
>>
>> Many thanks in advance,
>> Bizhan
>>
>> <ATT2118305.txt>
>>
>>
>> <lspci_output.txt>
>> <proc_pci.txt>
>> <u-boot.txt>
>

Re: pci_enable_device fails on MPC8541

[Kylo Ginsberg]

Bizhan,

I noticed that lspci reports SERR on the secondary side of the bridge
from bus 0 to bus 2.  Do you know what's causing SERR to be asserted?

Kylo

On 8/9/05, Bizhan Gholikhamseh (bgholikh) <bgholikh@cisco.com> wrote:
> Hi Kumar,
> I am using Linux 2.6.11, u-boot 1.1.2.
> I see failure in pci_enable_device with message:
> "PCI: Device 0000:02:01.0 not available because of resource collisions"
>=20
> I have attached three files:
> lspci_output.txt: out put of the "lspci -v"
> proc_pci.txt: output of the "cat /proc/pci"
> u-boot.txt: output of the "pci command at u-boot"
>=20
> Any help greatly appreciated,
> Bizhan
> -----Original Message-----
> From: Kumar Gala [mailto:kumar.gala@freescale.com]
> Sent: Monday, August 08, 2005 1:34 PM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: pci_enable_device fails on MPC8541
>=20
> Bizhan,
>=20
> A few questions:
>=20
> 1. what kernel version are you using on these boards:
> 2. can you do an lspci -v on the boards
>=20
> - kumar
>=20
> On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\))) wrote:
>=20
> > Hi All,
> > I am using two evaluation board from freescale, 8540ADS and MPC8541.
> > The same PCI driver is being compiled and loaded on both platforms.
> > The same PCI driver (developed by me) for DSP board compiled and
> > loaded on both platforms.
> >
> > When I type: "insmod C6415.ko" on 8541 board, I get the following
> > error:
> > "PCI: Device 0000:02:01.0 not available because of resource
> > collisions"
> > This messages is because of the execution of the generic PCI Linux
> > command:
> > "pci_enable_device(pdev)"
> > The same API has no problem on 8540ADS.
> >
> >
> >> From UBOOT I can see my device is on bus 3:
> >>
> > =3D> pci 3
> > Scanning PCI devices on bus 3
> > BusDev FUN    VendorID    DeviceID    Device Class    Sub-Class
> > ----------------------------------------------------------------------
> > --
> > --------------------
> > 03.01.00            0x104c    0xa106        .........
> >
> > Any idea why the insmod fails on one board and not on the other one?
> >
> > Many thanks in advance,
> > Bizhan
> >
> > <ATT2118305.txt>
> >
>=20
>=20
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
>=20
>

RE: pci_enable_device fails on MPC8541

[Bizhan Gholikhamseh (bgholikh)]

[-- Attachment #1: Type: text/plain, Size: 3041 bytes --]

 <<pci_boot.pdf>> Kumar,
We do not support or care about VIA IDE controller. I have enabled the
DEBUG flag and attached the debug messages during boot. This is for
8541E.
Regards,
Bizhan 

-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@freescale.com] 
Sent: Tuesday, August 09, 2005 4:11 PM
To: Bizhan Gholikhamseh (bgholikh)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: pci_enable_device fails on MPC8541

Do you need support for the VIA IDE controller?  I'm not sure if that is
causing you issues.

Also, can you try enabling DEBUG in arch/ppc/kernel/pci.c and send a
boot log.  I'm trying to figure out what is causing the resource
conflict.  It appears that the memory resource is reasonable, but there
could be possible conflict on the IO resource side.

Also, if you can send logs of the same thing from the working 8540 ADS
that would be helpful.

- kumar

On Aug 9, 2005, at 12:18 PM, Bizhan Gholikhamseh \(((bgholikh\))) wrote:

> Hi Kumar,
> I am using Linux 2.6.11, u-boot 1.1.2.
> I see failure in pci_enable_device with message:
> "PCI: Device 0000:02:01.0 not available because of resource 
> collisions"
>
> I have attached three files:
> lspci_output.txt: out put of the "lspci -v"
> proc_pci.txt: output of the "cat /proc/pci"
> u-boot.txt: output of the "pci command at u-boot"
>
> Any help greatly appreciated,
> Bizhan
> -----Original Message-----
> From: Kumar Gala [mailto:kumar.gala@freescale.com]
> Sent: Monday, August 08, 2005 1:34 PM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: pci_enable_device fails on MPC8541
>
> Bizhan,
>
> A few questions:
>
> 1. what kernel version are you using on these boards:
> 2. can you do an lspci -v on the boards
>
> - kumar
>
> On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\)))
> wrote:
>
>
>> Hi All,
>> I am using two evaluation board from freescale, 8540ADS and MPC8541.
>> The same PCI driver is being compiled and loaded on both platforms.
>> The same PCI driver (developed by me) for DSP board compiled and
>> loaded on both platforms.
>>
>> When I type: "insmod C6415.ko" on 8541 board, I get the following
>> error:
>> "PCI: Device 0000:02:01.0 not available because of resource
>> collisions"
>> This messages is because of the execution of the generic PCI Linux
>> command:
>> "pci_enable_device(pdev)"
>> The same API has no problem on 8540ADS.
>>
>>
>>
>>> From UBOOT I can see my device is on bus 3:
>>>
>>>
>> => pci 3
>> Scanning PCI devices on bus 3
>> BusDev FUN    VendorID    DeviceID    Device Class    Sub-Class
>> ---------------------------------------------------------------------

>> -
>> --
>> --------------------
>> 03.01.00            0x104c    0xa106        .........
>>
>> Any idea why the insmod fails on one board and not on the other one?
>>
>> Many thanks in advance,
>> Bizhan
>>
>> <ATT2118305.txt>
>>
>>
>> <lspci_output.txt>
>> <proc_pci.txt>
>> <u-boot.txt>
>

[-- Attachment #2: pci_boot.txt --]
[-- Type: text/plain, Size: 1457 bytes --]

PCI: Probing PCI hardware
PCI: bridge rsrc 0..ffffff (100), parent c0248588
PCI: reparented 8259 (master) [20..21] under PCI1 host bridge
PCI: reparented 8259 (slave) [a0..a1] under PCI1 host bridge
PCI: reparented 8259 edge control [4d0..4d1] under PCI1 host bridge
PCI: bridge rsrc 80000000..9fffffff (200), parent c024856c
PCI: bridge rsrc 0..ffff (101), parent c02e5038
PCI: reparented 8259 (master) [20..21] under PCI Bus #01
PCI: reparented 8259 (slave) [a0..a1] under PCI Bus #01
PCI: reparented 8259 edge control [4d0..4d1] under PCI Bus #01
PCI: bridge rsrc 9fe00000..9fefffff (200), parent c02e5054
PCI: bridge rsrc 9fd00000..9fdfffff (1201), parent c02e5054
PCI: bridge rsrc 0..ffff (101), parent c02e5038
PCI: reparented PCI Bus #01 [0..ffff] under PCI Bus #02
PCI: bridge rsrc 9fc00000..9fcfffff (200), parent c02e5054
PCI: bridge rsrc 9fb00000..9fbfffff (1201), parent c02e5054
PCI: bridge rsrc 1000000..1ffffff (100), parent c0248588
PCI: bridge rsrc a0000000..bfffffff (200), parent c024856c
PCI:0000:00:11.0: Resource 0: 9ffff000-9fffffff (f=200)
PCI:0000:01:02.1: Resource 4: 0000cc00-0000cc0f (f=101)
PCI:0000:01:02.2: Resource 4: 0000ffe0-0000ffff (f=101)
PCI:0000:01:02.3: Resource 4: 0000ffc0-0000ffdf (f=101)
PCI:0000:01:02.5: Resource 0: 0000fe00-0000feff (f=101)
PCI:0000:01:02.5: Resource 1: 0000fdfc-0000fdff (f=101)
PCI:0000:01:02.5: Resource 2: 0000fdf8-0000fdfb (f=101)
PCI:0000:01:02.6: Resource 0: 0000fc00-0000fcff (f=101)


[-- Attachment #3: pci_boot.pdf --]
[-- Type: application/octet-stream, Size: 8370 bytes --]

Re: pci_enable_device fails on MPC8541

[Kumar Gala]

It would be extremely helpful to get the output from the work MPC8540  
for lspci and cat /proc/pci.

Also, I forget if 2.6.11 has CDS VIA support, but if it does you can  
try disabling it by commenting out the calls to:
mpc85xx_cds_enable_via() & mpc85xx_cds_fixup_via() in arch/ppc/syslib/ 
ppc85xx_setup.c and see what happens.

- k

On Aug 10, 2005, at 10:58 AM, Bizhan Gholikhamseh \\((bgholikh\\))  
wrote:

>  <<pci_boot.pdf>> Kumar,
> We do not support or care about VIA IDE controller. I have enabled the
> DEBUG flag and attached the debug messages during boot. This is for
> 8541E.
> Regards,
> Bizhan
>
> -----Original Message-----
> From: Kumar Gala [mailto:kumar.gala@freescale.com]
> Sent: Tuesday, August 09, 2005 4:11 PM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: pci_enable_device fails on MPC8541
>
> Do you need support for the VIA IDE controller?  I'm not sure if  
> that is
> causing you issues.
>
> Also, can you try enabling DEBUG in arch/ppc/kernel/pci.c and send a
> boot log.  I'm trying to figure out what is causing the resource
> conflict.  It appears that the memory resource is reasonable, but  
> there
> could be possible conflict on the IO resource side.
>
> Also, if you can send logs of the same thing from the working 8540 ADS
> that would be helpful.
>
> - kumar
>
> On Aug 9, 2005, at 12:18 PM, Bizhan Gholikhamseh \(((bgholikh\)))  
> wrote:
>
>
>> Hi Kumar,
>> I am using Linux 2.6.11, u-boot 1.1.2.
>> I see failure in pci_enable_device with message:
>> "PCI: Device 0000:02:01.0 not available because of resource
>> collisions"
>>
>> I have attached three files:
>> lspci_output.txt: out put of the "lspci -v"
>> proc_pci.txt: output of the "cat /proc/pci"
>> u-boot.txt: output of the "pci command at u-boot"
>>
>> Any help greatly appreciated,
>> Bizhan
>> -----Original Message-----
>> From: Kumar Gala [mailto:kumar.gala@freescale.com]
>> Sent: Monday, August 08, 2005 1:34 PM
>> To: Bizhan Gholikhamseh (bgholikh)
>> Cc: linuxppc-embedded@ozlabs.org
>> Subject: Re: pci_enable_device fails on MPC8541
>>
>> Bizhan,
>>
>> A few questions:
>>
>> 1. what kernel version are you using on these boards:
>> 2. can you do an lspci -v on the boards
>>
>> - kumar
>>
>> On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\)))
>> wrote:
>>
>>
>>
>>> Hi All,
>>> I am using two evaluation board from freescale, 8540ADS and MPC8541.
>>> The same PCI driver is being compiled and loaded on both platforms.
>>> The same PCI driver (developed by me) for DSP board compiled and
>>> loaded on both platforms.
>>>
>>> When I type: "insmod C6415.ko" on 8541 board, I get the following
>>> error:
>>> "PCI: Device 0000:02:01.0 not available because of resource
>>> collisions"
>>> This messages is because of the execution of the generic PCI Linux
>>> command:
>>> "pci_enable_device(pdev)"
>>> The same API has no problem on 8540ADS.
>>>
>>>
>>>
>>>
>>>> From UBOOT I can see my device is on bus 3:
>>>>
>>>>
>>>>
>>> => pci 3
>>> Scanning PCI devices on bus 3
>>> BusDev FUN    VendorID    DeviceID    Device Class    Sub-Class
>>> -------------------------------------------------------------------- 
>>> -
>>>
>
>
>>> -
>>> --
>>> --------------------
>>> 03.01.00            0x104c    0xa106        .........
>>>
>>> Any idea why the insmod fails on one board and not on the other one?
>>>
>>> Many thanks in advance,
>>> Bizhan
>>>
>>> <ATT2118305.txt>
>>>
>>>
>>> <lspci_output.txt>
>>> <proc_pci.txt>
>>> <u-boot.txt>
>>>
>>
>>
>> <pci_boot.txt>
>> <pci_boot.pdf>
>

RE: pci_enable_device fails on MPC8541

[Bizhan Gholikhamseh (bgholikh)]

[-- Attachment #1: Type: text/plain, Size: 4111 bytes --]

Kumar,
Sorry it took a while. I have attached the 8540 PCI boot log and
/proc/pci. Also I found out the functions you mentioned are not used in
my environment.

Thanks,
Bizhan 

-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@freescale.com] 
Sent: Wednesday, August 10, 2005 9:06 AM
To: Bizhan Gholikhamseh (bgholikh)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: pci_enable_device fails on MPC8541

It would be extremely helpful to get the output from the work MPC8540
for lspci and cat /proc/pci.

Also, I forget if 2.6.11 has CDS VIA support, but if it does you can try
disabling it by commenting out the calls to:
mpc85xx_cds_enable_via() & mpc85xx_cds_fixup_via() in arch/ppc/syslib/
ppc85xx_setup.c and see what happens.

- k

On Aug 10, 2005, at 10:58 AM, Bizhan Gholikhamseh \\((bgholikh\\))
wrote:

>  <<pci_boot.pdf>> Kumar,
> We do not support or care about VIA IDE controller. I have enabled the

> DEBUG flag and attached the debug messages during boot. This is for 
> 8541E.
> Regards,
> Bizhan
>
> -----Original Message-----
> From: Kumar Gala [mailto:kumar.gala@freescale.com]
> Sent: Tuesday, August 09, 2005 4:11 PM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: pci_enable_device fails on MPC8541
>
> Do you need support for the VIA IDE controller?  I'm not sure if that 
> is causing you issues.
>
> Also, can you try enabling DEBUG in arch/ppc/kernel/pci.c and send a 
> boot log.  I'm trying to figure out what is causing the resource 
> conflict.  It appears that the memory resource is reasonable, but 
> there could be possible conflict on the IO resource side.
>
> Also, if you can send logs of the same thing from the working 8540 ADS

> that would be helpful.
>
> - kumar
>
> On Aug 9, 2005, at 12:18 PM, Bizhan Gholikhamseh \(((bgholikh\)))
> wrote:
>
>
>> Hi Kumar,
>> I am using Linux 2.6.11, u-boot 1.1.2.
>> I see failure in pci_enable_device with message:
>> "PCI: Device 0000:02:01.0 not available because of resource
>> collisions"
>>
>> I have attached three files:
>> lspci_output.txt: out put of the "lspci -v"
>> proc_pci.txt: output of the "cat /proc/pci"
>> u-boot.txt: output of the "pci command at u-boot"
>>
>> Any help greatly appreciated,
>> Bizhan
>> -----Original Message-----
>> From: Kumar Gala [mailto:kumar.gala@freescale.com]
>> Sent: Monday, August 08, 2005 1:34 PM
>> To: Bizhan Gholikhamseh (bgholikh)
>> Cc: linuxppc-embedded@ozlabs.org
>> Subject: Re: pci_enable_device fails on MPC8541
>>
>> Bizhan,
>>
>> A few questions:
>>
>> 1. what kernel version are you using on these boards:
>> 2. can you do an lspci -v on the boards
>>
>> - kumar
>>
>> On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\)))
>> wrote:
>>
>>
>>
>>> Hi All,
>>> I am using two evaluation board from freescale, 8540ADS and MPC8541.
>>> The same PCI driver is being compiled and loaded on both platforms.
>>> The same PCI driver (developed by me) for DSP board compiled and
>>> loaded on both platforms.
>>>
>>> When I type: "insmod C6415.ko" on 8541 board, I get the following
>>> error:
>>> "PCI: Device 0000:02:01.0 not available because of resource
>>> collisions"
>>> This messages is because of the execution of the generic PCI Linux
>>> command:
>>> "pci_enable_device(pdev)"
>>> The same API has no problem on 8540ADS.
>>>
>>>
>>>
>>>
>>>> From UBOOT I can see my device is on bus 3:
>>>>
>>>>
>>>>
>>> => pci 3
>>> Scanning PCI devices on bus 3
>>> BusDev FUN    VendorID    DeviceID    Device Class    Sub-Class
>>> --------------------------------------------------------------------

>>> -
>>>
>
>
>>> -
>>> --
>>> --------------------
>>> 03.01.00            0x104c    0xa106        .........
>>>
>>> Any idea why the insmod fails on one board and not on the other one?
>>>
>>> Many thanks in advance,
>>> Bizhan
>>>
>>> <ATT2118305.txt>
>>>
>>>
>>> <lspci_output.txt>
>>> <proc_pci.txt>
>>> <u-boot.txt>
>>>
>>
>>
>> <pci_boot.txt>
>> <pci_boot.pdf>
>

[-- Attachment #2: pci_boot_8540.txt --]
[-- Type: text/plain, Size: 482 bytes --]

PCI: Probing PCI hardware
PCI: bridge rsrc 0..ffffff (100), parent c0203818
PCI: bridge rsrc 80000000..9fffffff (200), parent c02037fc
PCI: bridge rsrc fff000..ffffff (101), parent c0293038
PCI: bridge rsrc 9f000000..9fffffff (200), parent c0293054
PCI: bridge rsrc 9ef00000..9effffff (1201), parent c0293054
PCI:0000:01:01.0: Resource 0: 9fc00000-9fffffff (f=1208)
PCI:0000:01:01.0: Resource 1: 9f000000-9f7fffff (f=200)
PCI:0000:01:01.0: Resource 2: 00fffff0-00ffffff (f=101)





[-- Attachment #3: proc_pci_8540.txt --]
[-- Type: text/plain, Size: 524 bytes --]


# cat /proc/pci

PCI devices found:
  Bus  0, device  21, function  0:
    PCI bridge: Texas Instruments PCI2050 PCI-to-PCI Bridge (rev 2).
      IRQ 98.
      Master Capable.  Latency=128.
  Bus  1, device   1, function  0:
    Non-VGA unclassified device: Texas Instruments TMS320C6205 Fixed Point DSP (rev 1).      IRQ 99.
      Master Capable.  Latency=128.
      Prefetchable 32 bit memory at 0x9fc00000 [0x9fffffff].
      Non-prefetchable 32 bit memory at 0x9f000000 [0x9f7fffff].
      I/O at 0xfffff0 [0xffffff].

Re: pci_enable_device fails on MPC8541

[Kumar Gala]

No problem.  I'm hunting around the problem, but trying to figure out  
exactly where the bug is.  What's a little odd is that in 2.6.11 we  
should have excluded all the devices that are on the VIA chipset.   
However, in the logs you sent me we see those devices. Part of the  
problem is that your TI DSP has its own P2P bridge on it.  Therefor  
the bus numbers for the devices start changing around a bit.

What is CONFIG_85xx_PCI2 set to in your .config?

Can you send me the output of the following on the 8555 CDS:
cat /proc/ioports
cat /proc/iomem

Also, if you feel daring, grab the latest 2.6.13-rc6 kernel and build  
it for 8555 CDS and see what happens.

Oh, is this card something standard or a custom thing?  The issue of  
having a card with P2P bridge on it has come up more than once.   
However, I'm not sure of any standard PC PCI cards do this (at least  
none of the simple cards we have do).  I'd like to see if we can find  
something that we could start testing with.

thanks

- kumar

On Aug 10, 2005, at 1:03 PM, Bizhan Gholikhamseh \(((bgholikh\))) wrote:

> Kumar,
> Sorry it took a while. I have attached the 8540 PCI boot log and
> /proc/pci. Also I found out the functions you mentioned are not  
> used in
> my environment.
>
> Thanks,
> Bizhan
>
> -----Original Message-----
> From: Kumar Gala [mailto:kumar.gala@freescale.com]
> Sent: Wednesday, August 10, 2005 9:06 AM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: pci_enable_device fails on MPC8541
>
> It would be extremely helpful to get the output from the work MPC8540
> for lspci and cat /proc/pci.
>
> Also, I forget if 2.6.11 has CDS VIA support, but if it does you  
> can try
> disabling it by commenting out the calls to:
> mpc85xx_cds_enable_via() & mpc85xx_cds_fixup_via() in arch/ppc/syslib/
> ppc85xx_setup.c and see what happens.
>
> - k
>
> On Aug 10, 2005, at 10:58 AM, Bizhan Gholikhamseh \\((bgholikh\\))
> wrote:
>
>
>>  <<pci_boot.pdf>> Kumar,
>> We do not support or care about VIA IDE controller. I have enabled  
>> the
>>
>
>
>> DEBUG flag and attached the debug messages during boot. This is for
>> 8541E.
>> Regards,
>> Bizhan
>>
>> -----Original Message-----
>> From: Kumar Gala [mailto:kumar.gala@freescale.com]
>> Sent: Tuesday, August 09, 2005 4:11 PM
>> To: Bizhan Gholikhamseh (bgholikh)
>> Cc: linuxppc-embedded@ozlabs.org
>> Subject: Re: pci_enable_device fails on MPC8541
>>
>> Do you need support for the VIA IDE controller?  I'm not sure if that
>> is causing you issues.
>>
>> Also, can you try enabling DEBUG in arch/ppc/kernel/pci.c and send a
>> boot log.  I'm trying to figure out what is causing the resource
>> conflict.  It appears that the memory resource is reasonable, but
>> there could be possible conflict on the IO resource side.
>>
>> Also, if you can send logs of the same thing from the working 8540  
>> ADS
>>
>
>
>> that would be helpful.
>>
>> - kumar
>>
>> On Aug 9, 2005, at 12:18 PM, Bizhan Gholikhamseh \(((bgholikh\)))
>> wrote:
>>
>>
>>
>>> Hi Kumar,
>>> I am using Linux 2.6.11, u-boot 1.1.2.
>>> I see failure in pci_enable_device with message:
>>> "PCI: Device 0000:02:01.0 not available because of resource
>>> collisions"
>>>
>>> I have attached three files:
>>> lspci_output.txt: out put of the "lspci -v"
>>> proc_pci.txt: output of the "cat /proc/pci"
>>> u-boot.txt: output of the "pci command at u-boot"
>>>
>>> Any help greatly appreciated,
>>> Bizhan
>>> -----Original Message-----
>>> From: Kumar Gala [mailto:kumar.gala@freescale.com]
>>> Sent: Monday, August 08, 2005 1:34 PM
>>> To: Bizhan Gholikhamseh (bgholikh)
>>> Cc: linuxppc-embedded@ozlabs.org
>>> Subject: Re: pci_enable_device fails on MPC8541
>>>
>>> Bizhan,
>>>
>>> A few questions:
>>>
>>> 1. what kernel version are you using on these boards:
>>> 2. can you do an lspci -v on the boards
>>>
>>> - kumar
>>>
>>> On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\)))
>>> wrote:
>>>
>>>
>>>
>>>
>>>> Hi All,
>>>> I am using two evaluation board from freescale, 8540ADS and  
>>>> MPC8541.
>>>> The same PCI driver is being compiled and loaded on both platforms.
>>>> The same PCI driver (developed by me) for DSP board compiled and
>>>> loaded on both platforms.
>>>>
>>>> When I type: "insmod C6415.ko" on 8541 board, I get the following
>>>> error:
>>>> "PCI: Device 0000:02:01.0 not available because of resource
>>>> collisions"
>>>> This messages is because of the execution of the generic PCI Linux
>>>> command:
>>>> "pci_enable_device(pdev)"
>>>> The same API has no problem on 8540ADS.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> From UBOOT I can see my device is on bus 3:
>>>>>
>>>>>
>>>>>
>>>>>
>>>> => pci 3
>>>> Scanning PCI devices on bus 3
>>>> BusDev FUN    VendorID    DeviceID    Device Class    Sub-Class
>>>> ------------------------------------------------------------------- 
>>>> -
>>>>
>
>
>>>> -
>>>>
>>>>
>>
>>
>>
>>>> -
>>>> --
>>>> --------------------
>>>> 03.01.00            0x104c    0xa106        .........
>>>>
>>>> Any idea why the insmod fails on one board and not on the other  
>>>> one?
>>>>
>>>> Many thanks in advance,
>>>> Bizhan
>>>>
>>>> <ATT2118305.txt>
>>>>
>>>>
>>>> <lspci_output.txt>
>>>> <proc_pci.txt>
>>>> <u-boot.txt>
>>>>
>>>>
>>>
>>>
>>> <pci_boot.txt>
>>> <pci_boot.pdf>
>>>
>>
>>
>> <pci_boot_8540.txt>
>> <proc_pci_8540.txt>
>

RE: pci_enable_device fails on MPC8541

[Bizhan Gholikhamseh (bgholikh)]

[-- Attachment #1: Type: text/plain, Size: 6013 bytes --]

HI Kumar,
I have attached the /proc/ioports and /proc/iomem for 8541E.
Also the CONFIG_ 85XX_PCI2 is set to yes.

Freescale does not support 2.6.13 so I am not able to update to that
version yet.

Thanks,
Bizhan

-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@freescale.com] 
Sent: Wednesday, August 10, 2005 12:11 PM
To: Bizhan Gholikhamseh (bgholikh)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: pci_enable_device fails on MPC8541

No problem.  I'm hunting around the problem, but trying to figure out
exactly where the bug is.  What's a little odd is that in 2.6.11 we  
should have excluded all the devices that are on the VIA chipset.   
However, in the logs you sent me we see those devices. Part of the
problem is that your TI DSP has its own P2P bridge on it.  Therefor the
bus numbers for the devices start changing around a bit.

What is CONFIG_85xx_PCI2 set to in your .config?

Can you send me the output of the following on the 8555 CDS:
cat /proc/ioports
cat /proc/iomem

Also, if you feel daring, grab the latest 2.6.13-rc6 kernel and build it
for 8555 CDS and see what happens.

Oh, is this card something standard or a custom thing?  The issue of  
having a card with P2P bridge on it has come up more than once.   
However, I'm not sure of any standard PC PCI cards do this (at least
none of the simple cards we have do).  I'd like to see if we can find
something that we could start testing with.

thanks

- kumar

On Aug 10, 2005, at 1:03 PM, Bizhan Gholikhamseh \(((bgholikh\))) wrote:

> Kumar,
> Sorry it took a while. I have attached the 8540 PCI boot log and 
> /proc/pci. Also I found out the functions you mentioned are not used 
> in my environment.
>
> Thanks,
> Bizhan
>
> -----Original Message-----
> From: Kumar Gala [mailto:kumar.gala@freescale.com]
> Sent: Wednesday, August 10, 2005 9:06 AM
> To: Bizhan Gholikhamseh (bgholikh)
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: pci_enable_device fails on MPC8541
>
> It would be extremely helpful to get the output from the work MPC8540 
> for lspci and cat /proc/pci.
>
> Also, I forget if 2.6.11 has CDS VIA support, but if it does you can 
> try disabling it by commenting out the calls to:
> mpc85xx_cds_enable_via() & mpc85xx_cds_fixup_via() in arch/ppc/syslib/

> ppc85xx_setup.c and see what happens.
>
> - k
>
> On Aug 10, 2005, at 10:58 AM, Bizhan Gholikhamseh \\((bgholikh\\))
> wrote:
>
>
>>  <<pci_boot.pdf>> Kumar,
>> We do not support or care about VIA IDE controller. I have enabled 
>> the
>>
>
>
>> DEBUG flag and attached the debug messages during boot. This is for 
>> 8541E.
>> Regards,
>> Bizhan
>>
>> -----Original Message-----
>> From: Kumar Gala [mailto:kumar.gala@freescale.com]
>> Sent: Tuesday, August 09, 2005 4:11 PM
>> To: Bizhan Gholikhamseh (bgholikh)
>> Cc: linuxppc-embedded@ozlabs.org
>> Subject: Re: pci_enable_device fails on MPC8541
>>
>> Do you need support for the VIA IDE controller?  I'm not sure if that

>> is causing you issues.
>>
>> Also, can you try enabling DEBUG in arch/ppc/kernel/pci.c and send a 
>> boot log.  I'm trying to figure out what is causing the resource 
>> conflict.  It appears that the memory resource is reasonable, but 
>> there could be possible conflict on the IO resource side.
>>
>> Also, if you can send logs of the same thing from the working 8540 
>> ADS
>>
>
>
>> that would be helpful.
>>
>> - kumar
>>
>> On Aug 9, 2005, at 12:18 PM, Bizhan Gholikhamseh \(((bgholikh\)))
>> wrote:
>>
>>
>>
>>> Hi Kumar,
>>> I am using Linux 2.6.11, u-boot 1.1.2.
>>> I see failure in pci_enable_device with message:
>>> "PCI: Device 0000:02:01.0 not available because of resource 
>>> collisions"
>>>
>>> I have attached three files:
>>> lspci_output.txt: out put of the "lspci -v"
>>> proc_pci.txt: output of the "cat /proc/pci"
>>> u-boot.txt: output of the "pci command at u-boot"
>>>
>>> Any help greatly appreciated,
>>> Bizhan
>>> -----Original Message-----
>>> From: Kumar Gala [mailto:kumar.gala@freescale.com]
>>> Sent: Monday, August 08, 2005 1:34 PM
>>> To: Bizhan Gholikhamseh (bgholikh)
>>> Cc: linuxppc-embedded@ozlabs.org
>>> Subject: Re: pci_enable_device fails on MPC8541
>>>
>>> Bizhan,
>>>
>>> A few questions:
>>>
>>> 1. what kernel version are you using on these boards:
>>> 2. can you do an lspci -v on the boards
>>>
>>> - kumar
>>>
>>> On Aug 8, 2005, at 1:12 PM, Bizhan Gholikhamseh \(((bgholikh\)))
>>> wrote:
>>>
>>>
>>>
>>>
>>>> Hi All,
>>>> I am using two evaluation board from freescale, 8540ADS and 
>>>> MPC8541.
>>>> The same PCI driver is being compiled and loaded on both platforms.
>>>> The same PCI driver (developed by me) for DSP board compiled and 
>>>> loaded on both platforms.
>>>>
>>>> When I type: "insmod C6415.ko" on 8541 board, I get the following
>>>> error:
>>>> "PCI: Device 0000:02:01.0 not available because of resource 
>>>> collisions"
>>>> This messages is because of the execution of the generic PCI Linux
>>>> command:
>>>> "pci_enable_device(pdev)"
>>>> The same API has no problem on 8540ADS.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> From UBOOT I can see my device is on bus 3:
>>>>>
>>>>>
>>>>>
>>>>>
>>>> => pci 3
>>>> Scanning PCI devices on bus 3
>>>> BusDev FUN    VendorID    DeviceID    Device Class    Sub-Class
>>>> -------------------------------------------------------------------
>>>> -
>>>>
>
>
>>>> -
>>>>
>>>>
>>
>>
>>
>>>> -
>>>> --
>>>> --------------------
>>>> 03.01.00            0x104c    0xa106        .........
>>>>
>>>> Any idea why the insmod fails on one board and not on the other 
>>>> one?
>>>>
>>>> Many thanks in advance,
>>>> Bizhan
>>>>
>>>> <ATT2118305.txt>
>>>>
>>>>
>>>> <lspci_output.txt>
>>>> <proc_pci.txt>
>>>> <u-boot.txt>
>>>>
>>>>
>>>
>>>
>>> <pci_boot.txt>
>>> <pci_boot.pdf>
>>>
>>
>>
>> <pci_boot_8540.txt>
>> <proc_pci_8540.txt>
>

[-- Attachment #2: proc_ioports_iomem.txt --]
[-- Type: text/plain, Size: 1456 bytes --]

# cat /proc/ioports
00000000-00ffffff : PCI1 host bridge
  00000000-0000ffff : PCI Bus #02
    00000000-0000ffff : PCI Bus #01
      00000020-00000021 : 8259 (master)
      00000060-0000006f : i8042
      000000a0-000000a1 : 8259 (slave)
      000004d0-000004d1 : 8259 edge control
      0000cc00-0000cc0f : 0000:01:02.1
      0000fc00-0000fcff : 0000:01:02.6
      0000fdf8-0000fdfb : 0000:01:02.5
      0000fdfc-0000fdff : 0000:01:02.5
      0000fe00-0000feff : 0000:01:02.5
      0000ffc0-0000ffdf : 0000:01:02.3
      0000ffe0-0000ffff : 0000:01:02.2
01000000-01ffffff : PCI2 host bridge
# cat /proc/iomem
80000000-9fffffff : PCI1 host bridge
  9ef00000-9effffff : PCI Bus #02
  9f000000-9fcfffff : PCI Bus #02
    9f000000-9f7fffff : 0000:02:01.0
    9f800000-9fbfffff : 0000:02:01.0
  9fd00000-9fdfffff : PCI Bus #01
  9fe00000-9fefffff : PCI Bus #01
  9ffff000-9fffffff : 0000:00:11.0
a0000000-bfffffff : PCI2 host bridge
e0003000-e0003fff : fsl-i2c1
e0004500-e0004507 : serial
e0004600-e0004607 : serial
e0021100-e002117f : fsl-dma0
e0021180-e00211ff : fsl-dma1
e0021200-e002127f : fsl-dma2
e0021280-e00212ff : fsl-dma3
e0024000-e0024fff : fsl-gianfar1
e0025000-e0025fff : fsl-gianfar2
e0030000-e003ffff : fsl-sec21
e0091300-e009131f : fsl-cpm-fcc1
e0091320-e009133f : fsl-cpm-fcc2
e0091380-e009139f : fsl-cpm-fcc1
e00913a0-e00913cf : fsl-cpm-fcc2
e0091860-e00918bf : fsl-cpm-i2c1
e0091aa0-e0091aff : fsl-cpm-spi1
e00e1000-e00e1fff : fsl-perfmon1