From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Linuxppc-dev Development <linuxppc-dev@ozlabs.org>,
Roderick Colenbrander <thunderbird2k@gmail.com>
Subject: Re: pci32 code - early_*config*
Date: Fri, 17 Apr 2009 19:05:12 +0200 [thread overview]
Message-ID: <1239987912.7210.17.camel@pasglop> (raw)
In-Reply-To: <5A611DAC-A7E2-4E96-A087-B9BFD8DF59F9@kernel.crashing.org>
On Fri, 2009-04-17 at 09:08 -0500, Kumar Gala wrote:
> The problem is that the "normal" PCI config access routines need a
> pci_bus. However we don't have one yet and we need to do PCI config
> cycles to the PHB before we call the remainder of the setup code to
> get one.
>
> We could all call our own ops directly and provide a fake bus but
> this
> is pretty much what the early routines do for us in a common way.
Ah right, slipped out of my mind. Oh well, easy to make the code
common, move it to pci-common.c
Cheers,
Ben.
next prev parent reply other threads:[~2009-04-17 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 6:17 pci32 code - early_*config* Kumar Gala
2009-04-17 7:25 ` Benjamin Herrenschmidt
2009-04-17 8:03 ` Roderick Colenbrander
2009-04-17 8:33 ` Benjamin Herrenschmidt
2009-04-17 14:08 ` Kumar Gala
2009-04-17 17:05 ` Benjamin Herrenschmidt [this message]
2009-04-17 17:38 ` 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=1239987912.7210.17.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=thunderbird2k@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.