linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Gary Thomas <gary@mlbassoc.com>
Subject: Re: PCI changes 2.6.26 => 2.6.28
Date: Tue, 21 Apr 2009 17:50:47 -0500	[thread overview]
Message-ID: <46B035C0-624F-41E4-BFDD-C16479CF8FC8@kernel.crashing.org> (raw)
In-Reply-To: <612CEF05-3EFB-4947-B5FC-B35C1F9568D7@kernel.crashing.org>

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

  reply	other threads:[~2009-04-21 22:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21 16:24 PCI changes 2.6.26 => 2.6.28 Gary Thomas
2009-04-21 20:30 ` Gary Thomas
2009-04-21 20:32   ` Gary Thomas
2009-04-21 20:33   ` Kumar Gala
2009-04-21 20:45     ` Gary Thomas
2009-04-21 22:22       ` Gary Thomas
2009-04-21 22:38         ` Kumar Gala
2009-04-21 22:50           ` Kumar Gala [this message]
2009-04-21 23:00             ` Gary Thomas
2009-04-21 23:41               ` Kumar Gala
2009-04-21 23:45                 ` Gary Thomas
2009-04-22  3:51                   ` Kumar Gala
2009-04-23 14:24                     ` Gary Thomas
2009-04-23 18:47                       ` Kumar Gala
2009-04-23 22:27                         ` Gary Thomas
2009-04-27 13:17                           ` Benjamin Herrenschmidt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46B035C0-624F-41E4-BFDD-C16479CF8FC8@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=gary@mlbassoc.com \
    --cc=linuxppc-dev@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).