From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Matthew Wilcox <matthew@wil.cx>, Alex Chiang <achiang@hp.com>,
jbarnes@virtuousgeek.org, linux-arch@vger.kernel.org,
Kyle McMartin <kyle@mcmartin.ca>, Tony Luck <tony.luck@intel.com>,
Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Jeff Dike <jdike@addtoit.com>,
linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
David Howells <dhowells@redhat.com>,
Paul Mundt <lethal@linux-sh.org>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Ingo Molnar <mingo@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH] PCI: remove pcibios_scan_all_fns()
Date: Tue, 23 Jun 2009 10:33:53 +1000 [thread overview]
Message-ID: <1245717233.4017.21.camel@pasglop> (raw)
In-Reply-To: <4A4019F9.4020702@goop.org>
On Mon, 2009-06-22 at 16:55 -0700, Jeremy Fitzhardinge wrote:
>
> I wonder if that would upset drivers. Assuming they can cope with just
> being given some functions, how could one generically make a function
> look present-but-dummy enough to not upset the driver?
Well, the dummy function would have a totally different vid/did, I think
that would work. In general, while I've seen drivers that -do- need to
know their real function number to get to the right registers, I haven't
seen much that also need to see function 0 "right" (or if they do, then
function 0 just needs to be plugged in the same partition and the whole
problem is somewhat moot).
Cheers,
Ben.
next prev parent reply other threads:[~2009-06-23 1:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 14:08 [PATCH] PCI: remove pcibios_scan_all_fns() Alex Chiang
2009-06-22 14:21 ` Kyle McMartin
2009-06-22 14:26 ` Ralf Baechle
2009-06-22 14:36 ` Matthew Wilcox
2009-06-22 14:34 ` Matthew Wilcox
2009-06-22 18:20 ` Jeremy Fitzhardinge
2009-06-22 18:30 ` Matthew Wilcox
2009-06-22 23:40 ` Benjamin Herrenschmidt
2009-06-23 19:08 ` Matthew Wilcox
2009-06-23 20:34 ` Jeremy Fitzhardinge
2009-06-23 20:56 ` Matthew Wilcox
2009-06-23 21:49 ` Benjamin Herrenschmidt
2009-06-23 22:24 ` Jeremy Fitzhardinge
2009-06-23 22:41 ` Benjamin Herrenschmidt
2009-06-23 22:53 ` Jeremy Fitzhardinge
2009-06-24 0:02 ` Benjamin Herrenschmidt
2009-06-24 10:30 ` Ian Campbell
2009-06-23 21:47 ` Benjamin Herrenschmidt
2009-06-22 23:55 ` Jeremy Fitzhardinge
2009-06-23 0:33 ` Benjamin Herrenschmidt [this message]
2009-06-23 1:43 ` Chris Wright
2009-06-23 2:22 ` Benjamin Herrenschmidt
2009-06-23 18:29 ` Avi Kivity
2009-06-22 15:29 ` Russell King - ARM Linux
2009-06-22 16:53 ` Arnd Bergmann
2009-06-23 16:43 ` Paul Mundt
2009-06-29 20:33 ` 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=1245717233.4017.21.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=achiang@hp.com \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jbarnes@virtuousgeek.org \
--cc=jdike@addtoit.com \
--cc=jeremy@goop.org \
--cc=kyle@mcmartin.ca \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=matthew@wil.cx \
--cc=mingo@redhat.com \
--cc=ralf@linux-mips.org \
--cc=tony.luck@intel.com \
--cc=ysato@users.sourceforge.jp \
/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