<<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:[EMAIL PROTECTED] Sent: Tuesday, August 09, 2005 4:11 PM To: Bizhan Gholikhamseh (bgholikh) Cc: linuxppc-embedded at 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 at freescale.com] > Sent: Monday, August 08, 2005 1:34 PM > To: Bizhan Gholikhamseh (bgholikh) > Cc: linuxppc-embedded at 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> > -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: pci_boot.txt Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050810/59c0c6a5/attachment.txt -------------- next part -------------- A non-text attachment was scrubbed... Name: pci_boot.pdf Type: application/octet-stream Size: 8370 bytes Desc: pci_boot.pdf Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050810/59c0c6a5/attachment.obj
