Re: PCI hotplug problems: how to debug?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Nov 04, 2009 at 06:39:16PM -0800, Yinghai Lu wrote:
> >> > >
> >> > > > On both the Trenton and Force computers, the BIOS assigns the PCI BAR
> >> > > > addresses towards the top of memory. Both assign addresses above
> >> > > > 0xF0000000.
> >> > > >
> >> > > > After running a hotplug on the Trenton computer, I have used a PCI logic
> >> > > > analyzer to confirm that no transactions accessing the PCI BAR's of the
> >> > > > hotplugged card make it onto the PCI bus. PCI configuration space still
> >> > > > works.
> >> > >
> 
> the broadcom chip has two peer root buses
> 
> looks like force:
> broadcom --->force --> powerpc hotplug controller
> 
> other one
> broadcom --->powerpc hotplug controller
> 
> if you have access to the doc with register for CNB20LE, you could
> create broadcom_bus.c like the one intel_bus.c
> 

Unfortunately, Google can't find a datasheet for that part anywhere. I
also tried "serverworks serverset" and "nb6635". :(

Ira
--
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

[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux