From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Roderick Colenbrander <thunderbird2k@gmail•com>
Cc: Linuxppc-dev Development <linuxppc-dev@ozlabs•org>
Subject: Re: pci32 code - early_*config*
Date: Fri, 17 Apr 2009 10:33:02 +0200 [thread overview]
Message-ID: <1239957182.7443.58.camel@pasglop> (raw)
In-Reply-To: <c8485d470904170103g35e331b0g95d83613ed4bc1f4@mail.gmail.com>
On Fri, 2009-04-17 at 10:03 +0200, Roderick Colenbrander wrote:
>
> There are cases when it is really needed (or you would have to access
> the address and data bus by hand). In my case I'm using a Xilinx PLB
> soft-core and if certain options in the configuration header aren't
> set (which aren't set by default) the soft-core is basically disabled.
> Cases like this look like valid cases in which early config should be
> used.
I still wonder whether we could just setup the pci_controller data
structure and use "normal" PCI config access routines...
Cheers,
Ben.
next prev parent reply other threads:[~2009-04-17 8:33 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 [this message]
2009-04-17 14:08 ` Kumar Gala
2009-04-17 17:05 ` Benjamin Herrenschmidt
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=1239957182.7443.58.camel@pasglop \
--to=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=thunderbird2k@gmail$(echo .)com \
/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