On Jan 28, 2009, at 3:31 AM, Benjamin Herrenschmidt wrote:
We are using the patch I emailed. It's ugly in that it hard-codes
the
Freescale vendor ID, but it works for us.
I guess I'm confused what the actual breakage is beyond some printk
messages.
We "fixup" the resources in fsl_pcibio
> > We are using the patch I emailed. It's ugly in that it hard-codes the
> > Freescale vendor ID, but it works for us.
>
> I guess I'm confused what the actual breakage is beyond some printk
> messages.
>
> We "fixup" the resources in fsl_pcibios_fixup_bus() so Ben's change
> shouldn't hav
On Jan 27, 2009, at 12:13 PM, Andrew Klossner wrote:
Kumar, you wrote:
Any resolution to all this.. Not exactly sure what change impacts
things and what part of our screwy HW is causing issues.
The change in question is commit
b556151110ff003ce77d84597400c84824690ccf.
The fundamental pr
On Wed, 2009-01-14 at 11:48 -0800, Andrew Klossner wrote:
> When I moved from 2.6.27 to 2.6.28, one of my devices didn't work
> until I devised the attached patch. The kernel disallowed PCI I/O
> space resources behind the pseudo-bridge in the Freescale MPC8545
> because that bridge's config-space
When I moved from 2.6.27 to 2.6.28, one of my devices didn't work
until I devised the attached patch. The kernel disallowed PCI I/O
space resources behind the pseudo-bridge in the Freescale MPC8545
because that bridge's config-space registers incorrectly report that
it doesn't forward I/O space tr
