public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed

From: Trevor Anderson <tanderson@vmetro•com>
To: linuxppc-embedded@ozlabs•org
Subject: Correct way to adjust PCI resource allocations?
Date: Thu, 12 Jun 2008 15:14:31 -0700 (PDT)	[thread overview]
Message-ID: <17810852.post@talk.nabble.com> (raw)


Hi,

I'm hoping somebody can tell me the correct way to change the memory
resources allocated to particular PCI buses/devices at startup?

I'm developing a card (MPC8641D, 2.6.25 kernel) that includes a PCI/X-VMEBus
bridge, and the driver requires that it have a chunk of [prefetchable] PCI
memory space available to it. There is nothing on the chip that says so: it
has a single BAR that covers its configuration registers, but nothing else.

So: I need a way to declare an additional memory requirement for this
particular device that will wend its way back through the chain of PCIe and
PCIX buses to the root.

So far I've been using a platform-specific "pcibios_fixup_resources"
function that simply writes-in my new requirement, in conjunction with
"ppc_pci_flags = PPC_PCI_REASSIGN_ALL_RSRC", as a new resource entry in the
device's pci_device structure. And this has been working well, so far. But
I've discovered that fitting an XMC/PMC card to my board mucks things up -
the resource allocations fail. The XMC/PMC card appears on the same PCI/X
bus as the VME bridge. 

This leads me to think I've not been using the correct method all along, but
happened to hit lucky until now.

What is the right way to do this?
Is pcibios_fixup_resources even meant to do something like this?

Any help gratefully welcomed.

Cheers,

- Trevor Anderson <tanderson@vmetro•com>

-- 
View this message in context: http://www.nabble.com/Correct-way-to-adjust-PCI-resource-allocations--tp17810852p17810852.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

                 reply	other threads:[~2008-06-12 22:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=17810852.post@talk.nabble.com \
    --to=tanderson@vmetro$(echo .)com \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox