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
>
> 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 syste
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
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 0x1
CONFIG_SYS_PCIE2_IO_PHYS 0xFFC0
#define CONFIG_SYS_PCIE2_IO_SIZE 0x0001/* 64k */
I'd really appreciate I you could take a look at it
Thanx alot in advance
Davide
2012/9/24 Davide Viti
> Hi,
> does the output I've included show anything wrong
calling quirk_usb_early_handoff+0x0/0x6ac
2012/9/26 Kumar Gala
>
> > 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 adv
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
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,
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,
it turns out that if define CONFIG_PCI_NOSCAN in u-boot (as per [1]), the
devide behind the second controller is detected by the Linux kernel.
Would
you suggest any particular patch I should apply to fix this (I'm using kernel
2.6.34)
thanx alot in advance
Davide
[1] http://permalink.gma
(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 behi
11 matches
Mail list logo
