public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc•com>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: PCI changes 2.6.26 => 2.6.28
Date: Tue, 21 Apr 2009 14:45:33 -0600	[thread overview]
Message-ID: <49EE306D.3000401@mlbassoc.com> (raw)
In-Reply-To: <29EEEBDE-B87C-4073-9967-E1DA7EFB0B0B@kernel.crashing.org>

Kumar Gala wrote:
> 
> On Apr 21, 2009, at 3:30 PM, Gary Thomas wrote:
> 
>> The [two] big differences I see are that the video card (00:0d.0)
>> is being assigned 0xC0000000, which lspci marks as "virtual".
>> I think I've had trouble in the past with memory regions which
>> started at 0 relative to the PCI space.  Also "virtual" concerns me.
>>
>> Does this spark any ideas from anyone?
> 
> Doesn't ring any bells.  What does cat /proc/iomem look like between the
> two kernels.

About what I gleaned from lspci. The working 2.6.26 kernel has
space mapped in the controller (exposed memory window, I think)
and the video card got moved down accordingly.

---------------------------------- 2.6.26
c0000000-cfffffff : /pci@ff008500
  c0000000-c7ffffff : 0000:00:00.0
  c8000000-cbffffff : 0000:00:0c.0
    c8000000-cbffffff : CoralP_fb
  cc000000-cc0fffff : 0000:00:00.0
  cc100000-cc11ffff : 0000:00:0b.0
  cc120000-cc12ffff : 0000:00:0a.0
  cc130000-cc13ffff : 0000:00:0a.0
  cc140000-cc140fff : 0000:00:0b.0
    cc140000-cc140fff : sata_promise
  cc141000-cc141fff : 0000:00:0d.0
    cc141000-cc141fff : ohci_hcd
  cc142000-cc142fff : 0000:00:0d.1
    cc142000-cc142fff : ohci_hcd
  cc143000-cc1430ff : 0000:00:0d.2
    cc143000-cc1430ff : ehci_hcd
  cc143100-cc143100 : 0000:00:00.0
f0000000-f1ffffff : f0000000.flash
ff000200-ff0002ff : wdt
ff003000-ff0030ff : i2c
ff003100-ff0031ff : i2c
ff004500-ff004507 : serial
ff004600-ff004607 : serial
ff022000-ff022fff : usb
  ff022000-ff022fff : ehci_hcd
ff023000-ff023fff : usb
  ff023000-ff023fff : usb
    ff023000-ff023fff : ehci_hcd
ff024000-ff024fff : ethernet
  ff024520-ff02453f : mdio
ff025000-ff025fff : ethernet

---------------------------------- 2.6.28
c0000000-cfffffff : /pci@ff008500
  c0000000-c3ffffff : 0000:00:0c.0
    c0000000-c3ffffff : CoralP_fb
  c4000000-c401ffff : 0000:00:0b.0
  c4020000-c402ffff : 0000:00:0a.0
  c4030000-c403ffff : 0000:00:0a.0
  c4040000-c4040fff : 0000:00:0b.0
    c4040000-c4040fff : sata_promise
  c4041000-c4041fff : 0000:00:0d.0
    c4041000-c4041fff : ohci_hcd
  c4042000-c4042fff : 0000:00:0d.1
    c4042000-c4042fff : ohci_hcd
  c4043000-c40430ff : 0000:00:0d.2
    c4043000-c40430ff : ehci_hcd
f0000000-f1ffffff : f0000000.flash
ff004500-ff004507 : serial
ff004600-ff004607 : serial
ff022000-ff022fff : usb
  ff022000-ff022fff : ehci_hcd
ff023000-ff023fff : usb
  ff023000-ff023fff : usb
    ff023000-ff023fff : ehci_hcd
ff024000-ff024fff : ethernet
  ff024520-ff02453f : mdio
ff025000-ff025fff : ethernet

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

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

  reply	other threads:[~2009-04-21 20:45 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 [this message]
2009-04-21 22:22       ` Gary Thomas
2009-04-21 22:38         ` Kumar Gala
2009-04-21 22:50           ` Kumar Gala
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=49EE306D.3000401@mlbassoc.com \
    --to=gary@mlbassoc$(echo .)com \
    --cc=galak@kernel$(echo .)crashing.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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