On Tue, Jul 10, 2012 at 4:09 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote: > On Tue, Jul 10, 2012 at 2:42 PM, Joakim Tjernlund > <joakim.tjernlund@xxxxxxxxxxxx> wrote: >> yhlu.kernel@xxxxxxxxx wrote on 2012/07/10 20:22:09: >> >>> >>> On Tue, Jul 10, 2012 at 10:29 AM, Joakim Tjernlund >>> <joakim.tjernlund@xxxxxxxxxxxx> wrote: >>> > >>> > I got an PCIe device that is woken up by user space, clocks needs to configured in various ways before the >>> > device enables its PCIe interface. >>> > >>> > The device is connected to a built in root bridge on a P2010(mpc85xx) CPU. >>> > To enable HP in Linux we need to apply some minor hacks. >>> >>> can you post lspci -vvxxx -s BB:DD:F of the two devices? >> >> Not really, this is an embedded device with limited SW. I got >> busybox and its lspci but that is very limited: >> # > ./busybox lspci -mk >> 00:00.0 "Class 0604" "1957" "0079" "0000" "0000" "pcieport" >> 01:00.0 "Class 0200" "14e4" "b540" "14e4" "b540" >> >> Does that tell you anything? > > No. Can you compile lspci util as static and run it ? You might also be able to get this info as console output by booting with "pci=earlydump". -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
