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
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, can you
try hack it to 1.
is this what y
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
