LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Luong Ngo" <luong.ngo@gmail.com>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: MPC8343: PCI resource allocation questions
Date: Wed, 25 Oct 2006 00:16:41 -0700	[thread overview]
Message-ID: <1b2aacd80610250016q4bcc5f9bm467ef09022ce1285@mail.gmail.com> (raw)
In-Reply-To: <4BF669F6-7A28-4915-9DFF-0B00CC04E242@kernel.crashing.org>

[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]

Would you mind explain me the last question in previous email?

  You are not leaving any memory space for any of the onchip devices,
the error messages are because the regions of memory that the devices
are expected to be at are already occupied by the PCI space.

Isn't it the PCI IO and PCI MEM space are separated from local memory space?
I think I see the global IO resource and MEM resource have the range of 0x0
- 0xFFFFFFFF.

Thanks,
Luong Ngo

On 10/24/06, Kumar Gala <galak@kernel.crashing.org> wrote:
>
>
> > I'm a bit confused here. If the host bridge is ignored/excluded,
> > then the region size in BARs will not be allocated corresponding
> > resource by the PCI subsystem, then how would other PCI devices in
> > the slots could be allocated in the BAR's range? If I understand
> > correctly, the PCI devices's resources are allocated based on the
> > bridge resource, which is assigned statically by PCI subsystem
> > using hose->mem_space and hose->io_space instead of reading it from
> > the BARs. Maybe you are saying in the case the CPU is in agent mode
> > and its PCI host bridge is functioning as a PCI-PCI bridge?
>
> The problem is the host bridge shouldn't be included in BAR
> assignment since its the host bridge.  The problem is FSL devices
> show up when they scan themselves and the kernel then tries to
> allocate resources to them as if they were any other device.
>
> you are correct, the pci subsystem is setup via the hose structure
> and not by trying to read BARs on the host controller itself.
>
> - kumar
>

[-- Attachment #2: Type: text/html, Size: 2105 bytes --]

  reply	other threads:[~2006-10-25  7:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25  3:49 MPC8343: PCI resource allocation questions Luong Ngo
2006-10-25  4:35 ` Kumar Gala
2006-10-25  5:46   ` Luong Ngo
2006-10-25  6:39     ` Kumar Gala
2006-10-25  7:16       ` Luong Ngo [this message]
2006-10-25 14:06         ` Kumar Gala

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=1b2aacd80610250016q4bcc5f9bm467ef09022ce1285@mail.gmail.com \
    --to=luong.ngo@gmail.com \
    --cc=galak@kernel.crashing.org \
    --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