public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Paul Mackerras <paulus@samba.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Issues with /proc/bus/pci
Date: Tue, 23 Mar 2004 15:02:16 +1100	[thread overview]
Message-ID: <1080014534.23717.92.camel@gaston> (raw)
In-Reply-To: <20040322194759.7a38ffe9.davem@redhat.com>

On Tue, 2004-03-23 at 14:47, David S. Miller wrote:
> On Tue, 23 Mar 2004 13:40:11 +1100
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> 
> > What do you think ?
> 
> Ok, it does sound like we need something else.
> 
> Another idea is to always at least provide a "virtual" host
> bridge on these weird platforms you mention.  You control
> the PCI config space etc. operations, so you could handle
> the virtual host bridge correctly right?

Yes. Though I'm not sure i like the idea.

Note that I don't have a platform affected by this problem at hand
(except the G5 for which I can tweak to make the HT host show up).
I have to double check some of the weirdest embedded PPC setups though,
those "hiding" the host bridge should have all been converted to just
hide it's BARs by now hopefully. But the theorical problem persists.

And it's still not convenient for userland things that need to access
one video card knowing it's PCI ID to have to iterate around to find
the host bridge, but I can live with that ;) Actually, for my specific
need for this softboot thing, it is powermac specific, so I can just
hack the ppc port to always acccept a mapping of the low 0x400 of IO
space from any PCI device... (provided those are actually in the host
bridge resources).

I'll see what I can do on our side

Ben.



  reply	other threads:[~2004-03-23  4:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23  2:06 Issues with /proc/bus/pci Benjamin Herrenschmidt
2004-03-23  2:31 ` David S. Miller
2004-03-23  2:40   ` Benjamin Herrenschmidt
2004-03-23  3:47     ` David S. Miller
2004-03-23  4:02       ` Benjamin Herrenschmidt [this message]
2004-03-23  4:12       ` Benjamin Herrenschmidt
2004-03-23  2:44 ` Jesse Barnes

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=1080014534.23717.92.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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