Hi Kumar,
I try to summarize the problem in the hope to fix it for good:
Linux Kernel (2.6.34-6) did not detect one of the two pci devices
that instead u-boot could "see".
This was worakounded by defining CONFIG_PCI_NOSCAN in u-boot as per [1]
To find out the root cause of the problem, you've sugg
Hi Kumar,
On Fri, Oct 05, 2012 at 07:47:24AM -0500, Kumar Gala wrote:
>
> On Oct 5, 2012, at 3:54 AM, Davide Viti wrote:
>
> >> On Oct 4, 2012, at 7:24 AM, Davide Viti wrote:
> >>
> >>> Hi,
> >>> it turns out that if define CONFIG_PCI_NOSCAN in u-boot (as per [1]), the
> >>> device behind the s
On Oct 5, 2012, at 3:54 AM, Davide Viti wrote:
> (just realized I did not send this to the mailing list: sorry for the noise)
>
> Hi Kumar,
>
> 2012/10/4 Kumar Gala :
>>
>> On Oct 4, 2012, at 7:24 AM, Davide Viti wrote:
>>
>>> Hi,
>>> it turns out that if define CONFIG_PCI_NOSCAN in u-boot (a
(just realized I did not send this to the mailing list: sorry for the noise)
Hi Kumar,
2012/10/4 Kumar Gala :
>
> On Oct 4, 2012, at 7:24 AM, Davide Viti wrote:
>
>> Hi,
>> it turns out that if define CONFIG_PCI_NOSCAN in u-boot (as per [1]), the
>> device behind the second controller is detected
There's some minor setting difference
that I'm guessing is causing issues.
- k
>
>> Messaggio originale
>> Da:
> zino...@tiscali.it
>> Data: 28/09/2012 16.48
>> A:
>> Cc:
>
>> Ogg: R: Re: PCI device not working
>>
>> Hi
http://permalink.gmane.org/gmane.
linux.ports.ppc.embedded/20140
>Messaggio originale
>Da:
zino...@tiscali.it
>Data: 28/09/2012 16.48
>A:
>Cc:
>Ogg: R: Re: PCI device not working
>
>Hi
Kumar,
>
>>
>>It was, can you figure out in u-boot what exact config read
Hi Kumar,
>
>It was, can you figure out in u-boot what exact config read on
the bus would return the correct thing.
>
>The fact that when we probe the
device at 0001:03 we should get back something like cfg_data=0xabba1b65
>
here
follow some details about what is going on inside u-boot; verbos
On Sep 27, 2012, at 8:14 AM, Davide Viti wrote:
> Hi Kumar,
>
>> Messaggio originale
>> Da: ga...@kernel.crashing.org
>> Data:
> 27/09/2012 14.27
>> A: "Davide Viti"
>> Cc: ozlabs.org>
>> Ogg: Re: PCI device not working
>&
Hi Kumar,
>Messaggio originale
>Da: ga...@kernel.crashing.org
>Data:
27/09/2012 14.27
>A: "Davide Viti"
>Cc:
>Ogg: Re: PCI device not working
>
...
>Can you see what bus_no
actually gets set to in the case we scan 0001:03 ?
>
>If its set to 03,
On Sep 27, 2012, at 6:43 AM, Davide Viti wrote:
> Hi,
>
>> So its odd that scanning of the second bus didn't report any devices. Do
> you have code that implements ppc_md.pci_exclude_device ?
>
> not that I'm aware
> of
>
>> You might also want to put some code in the indirect PCI ops (indi
Hi,
>So its odd that scanning of the second bus didn't report any devices. Do
you have code that implements ppc_md.pci_exclude_device ?
not that I'm aware
of
>You might also want to put some code in the indirect PCI ops (indirect.c)
to see what actual values you are getting from various indi
On Sep 26, 2012, at 10:25 AM, Davide Viti wrote:
> Hi,
> as you've suggested, I've added a printout inside fsl_pcie_check_link() which
> is called twice and returns 0 both times.
> Here follows the PCI-related part of dmesg with some extra printouts enabled.
>
> thank you,
> Davide
So its odd
Hi,
as you've suggested, I've added a printout inside fsl_pcie_check_link()
which is called twice and returns 0 both times.
Here follows the PCI-related part of dmesg with some extra printouts
enabled.
thank you,
Davide
...
Adding PCI host bridge /pcie@ffe09000
*** [/pcie@ffe09000] fsl_pcie_check
> 2012/9/24 Davide Viti
> Hi,
> does the output I've included show anything wrong or should I post something
> else to help identifying the cause of the problem?
>
> thank you in advance,
> Davide
>
> 2012/9/21 Davide Viti
> I mean there are two controllers and both of them have a device "sub
Here are the settings for PCI we currently have in uboot:
#define CONFIG_PCI 1/* Enable PCI/PCIE */
#define CONFIG_PCIE1 1/* PCIE controler 1
(slot 1) */
#define CONFIG_PCIE2 1/* PCIE controler 2
(slot 2) */
Hi,
does the output I've included show anything wrong or should I post
something else to help identifying the cause of the problem?
thank you in advance,
Davide
2012/9/21 Davide Viti
> I mean there are two controllers and both of them have a device
> "subtended" (both 0x1b65:0xabba).
> u-boot c
2012/9/21 Davide Viti
> I mean there are two controllers and both of them have a device
> "subtended" (both 0x1b65:0xabba).
> u-boot can see both devices, linux detects only the device attached to the
> first controller.
>
> Here's the output of lspci and /proc/iomem :
>
> root@(none):/# lspci -v
I mean there are two controllers and both of them have a device "subtended"
(both 0x1b65:0xabba).
u-boot can see both devices, linux detects only the device attached to the
first controller.
Here's the output of lspci and /proc/iomem :
root@(none):/# lspci -v
:00:00.0 Class 0604: Device 1957
On Sep 21, 2012, at 6:33 AM, Davide Viti wrote:
> Hi,
> I'm working on a custom board based on P1020 with two (identical) PCI devices
> attached;
> The work is derived from another board with a single instance of that device.
> The system is based on u-boot-2009.11 and Linux 2.6.34.6
>
> The "p
Hi,
I'm working on a custom board based on P1020 with two (identical) PCI
devices attached;
The work is derived from another board with a single instance of that
device.
The system is based on u-boot-2009.11 and Linux 2.6.34.6
The "pci" command on u-boot, shows me both the PCI controllers and
the
20 matches
Mail list logo
