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:
quoted
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:
quoted
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.
quoted
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
--------------------------------------------------------------------
quoted
quoted
-
quoted
quoted
-
--
--------------------
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>
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:
quoted
<<pci_boot.pdf>> Kumar,
We do not support or care about VIA IDE controller. I have enabled
the
quoted
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
quoted
that would be helpful.
- kumar
On Aug 9, 2005, at 12:18 PM, Bizhan Gholikhamseh \(((bgholikh\)))
wrote:
quoted
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:
quoted
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.
quoted
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
-------------------------------------------------------------------
-
quoted
quoted
quoted
-
quoted
quoted
-
--
--------------------
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>