On Oct 3, 2008, at 11:27 AM, Anton Vorontsov wrote:
On Fri, Oct 03, 2008 at 11:14:18AM -0500, Kumar Gala wrote:
On Oct 3, 2008, at 11:08 AM, Anton Vorontsov wrote:
In the standalone setup the board's CPLD disables the PCI internal
arbiter, thus any access to the PCI bus will hang the board.
On Fri, Oct 03, 2008 at 11:14:18AM -0500, Kumar Gala wrote:
>
> On Oct 3, 2008, at 11:08 AM, Anton Vorontsov wrote:
>
>> In the standalone setup the board's CPLD disables the PCI internal
>> arbiter, thus any access to the PCI bus will hang the board.
>>
>> When there is no PCI arbiter on the bus t
On Oct 3, 2008, at 11:08 AM, Anton Vorontsov wrote:
In the standalone setup the board's CPLD disables the PCI internal
arbiter, thus any access to the PCI bus will hang the board.
When there is no PCI arbiter on the bus the u-boot adds
status = "broken (no arbiter)" property into the PCI contr
In the standalone setup the board's CPLD disables the PCI internal
arbiter, thus any access to the PCI bus will hang the board.
When there is no PCI arbiter on the bus the u-boot adds
status = "broken (no arbiter)" property into the PCI controller's
node, and so marks the PCI controller as unavail
