linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Roderick Colenbrander <thunderbird2k@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linuxppc-dev Development <linuxppc-dev@ozlabs.org>
Subject: Re: pci32 code - early_*config*
Date: Fri, 17 Apr 2009 10:03:52 +0200	[thread overview]
Message-ID: <c8485d470904170103g35e331b0g95d83613ed4bc1f4@mail.gmail.com> (raw)
In-Reply-To: <1239953159.7443.33.camel@pasglop>

On Fri, Apr 17, 2009 at 9:25 AM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
> On Wed, 2009-04-15 at 01:17 -0500, Kumar Gala wrote:
>> Ben,
>>
>> I was looking at what I need to get some additional bits of PCI code
>> building w/your ppc64 booke patches. =A0One thing it looks like we need
>> is the early config cycle code. =A0The question I have is do we think we
>> still need the null_ops support? =A0Also do we think we every get called
>> with a NULL hose?
>>
>> This is fake_pci_bus() in arch/powerpc/kernel/pci_32.c
>
> Hrm.
>
> I'm not fan of the early config stuff, remind me why we need it ?
>
> Ben.
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>

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.

Roderick Colenbrander

  reply	other threads:[~2009-04-17  8:03 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 [this message]
2009-04-17  8:33     ` Benjamin Herrenschmidt
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=c8485d470904170103g35e331b0g95d83613ed4bc1f4@mail.gmail.com \
    --to=thunderbird2k@gmail.com \
    --cc=benh@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;
as well as URLs for NNTP newsgroup(s).