linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ishizaki Kou <kou.ishizaki@toshiba.co.jp>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 14/16] Resource assignments for PCI devices on Celleb
Date: Sat, 18 Nov 2006 09:14:59 +1100	[thread overview]
Message-ID: <1163801699.5826.35.camel@localhost.localdomain> (raw)
In-Reply-To: <200611171014.kAHAEPKA011876@toshiba.co.jp>

\
> This is a temporary workaround for following problem.
>    
> On Celleb, values of PCI base addresses of PCI devices which are not
> described in device tree are not initialized before linux starts. So
> we use pci_bus_assign_resources() later to assign resources for them 
> at ppc_md.pcibios_fixup(). But by original code, when
> ppc_md.pcibios_fixup() is called, resources are already claimed and
> pci_bus_assign_resource() does not work to assign resources.
> 
> It may not be a good idea to call pci_bus_assign_resources() at the
> timing of ppc_md.pcibios_fixup(), but we did not find an alternative
> idea.

Hrm.. not everything should be claimed... there should be some space
left to assign remaining devices. I need to look into it. There are
several non resolved issues unfortunately with the ppc64 PCI code vs.
assigning resources. (Well, the issues are with the generic code in fact
which is what ppc64 uses. It tends to not work very well on setups where
some resources have already been assigned and some not).

Ben.

  reply	other threads:[~2006-11-17 22:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 10:14 [PATCH 14/16] Resource assignments for PCI devices on Celleb Ishizaki Kou
2006-11-17 22:14 ` Benjamin Herrenschmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-15  9:58 Ishizaki Kou
2006-11-15 23:56 ` 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=1163801699.5826.35.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=kou.ishizaki@toshiba.co.jp \
    --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).