From: "David S. Miller" <davem@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: paulus@samba.org, linux-kernel@vger.kernel.org
Subject: Re: Issues with /proc/bus/pci
Date: Mon, 22 Mar 2004 19:47:59 -0800 [thread overview]
Message-ID: <20040322194759.7a38ffe9.davem@redhat.com> (raw)
In-Reply-To: <1080009609.23717.81.camel@gaston>
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?
next prev parent reply other threads:[~2004-03-23 3:48 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 [this message]
2004-03-23 4:02 ` Benjamin Herrenschmidt
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=20040322194759.7a38ffe9.davem@redhat.com \
--to=davem@redhat.com \
--cc=benh@kernel.crashing.org \
--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