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.
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 unavailable.
Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]>
---
On Thu, Oct 02, 2008 at 02:48:44PM -0500, Kumar Gala wrote:
Can you add to the commit message something about using the 'status
field in the device tree to determine if the pci controller is
available'
Something like this?
Thanks,
yes, but should we just have "status = disabled" since that is the
effect?
I don't know, should we? For the unavailable/disabled case the status
can be anything but not 'ok' or 'okay' (the only status values for the
available devices). So if we can encode the reason, why not do this?
that works for me, just add the fact to the commit msg that the "valid
status's are 'ok' and 'okay' and everything else is treated as "not
available or disabled"
- k
_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev
