PCI changes 2.6.26 => 2.6.28

Kumar Gala galak at kernel.crashing.org
Wed Apr 22 08:50:47 EST 2009


>>> I'm still looking into how the PCI address register for the video
>>> card did not get written, even though the system obviously thinks
>>> it did (hence "virtual")
>>>
>>
>> It most definitely has something to do with 0xC0000000 being
>> assigned to the video card.  I changed my DTS to move everything
>> up (started the whole space at 0xC4000000) and the video card
>> came to life!  Of course, I'm not interested in this hack,
>> so the simplest thing would be to figure out why 2.6.26 allocated
>> that outgoing window and 2.6.28 doesn't
>
> So I think the difference is due to the change in PCI code between  
> 2.6.26 and .28 for 83xx.  If you notice we exclude the FSL device  
> in .26 you have:
>
>>> c0000000-c7ffffff : 0000:00:00.0
>
> and in .28 its gone.  This accounts for the allocation differences.   
> What I don't get is why the behavior would vary based on address.
>
> Can you dump out the PCI inbound/outbound registers.  I have a  
> theory as to what's going on and want to confirm it.

Also, what's your .dts look like for the PCI node.

- k



More information about the Linuxppc-dev mailing list