All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jake Moilanen <moilanen@austin.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, greg@kroah.com, linux-kernel@vger.kernel.org,
	linuxppc64-dev@lists.linuxppc.org
Subject: Re: Fw: [PATCH][2.6] PCI Scan all functions
Date: Fri, 30 Jan 2004 08:10:08 -0600	[thread overview]
Message-ID: <1075471807.679.178.camel@magik> (raw)
In-Reply-To: <20040129153015.0e77f8e7.akpm@osdl.org>

> Could you please send me a changelog description for this patch?  A bit of
> background for posterity, so other kernel developers can come in a year
> hence and answer the question "what's all this about then?".  Thanks.

Sure.  

On a ppc64 logically partitioned system, there can be a setup where
function 0 of a PCI-PCI bridge is assigned to one partition and
(for example) function 2 is assigned to a second partition.  On the
second partition, it would appear that function 0 does not exist, but
function 2 does.  If all the functions are not scanned, everything under
function 2 would not be detected.

This patch allows devices that don't respond to function 0, but do
respond to other functions to be marked with a quirk and have all of
their functions scanned.  

Thanks,
Jake


      reply	other threads:[~2004-01-30 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040127130803.10b666f3.akpm@osdl.org>
     [not found] ` <Pine.LNX.4.58.0401271345060.10794@home.osdl.org>
     [not found]   ` <1075241556.681.19.camel@magik>
     [not found]     ` <Pine.LNX.4.58.0401271428340.10794@home.osdl.org>
     [not found]       ` <1075247559.672.33.camel@magik>
     [not found]         ` <Pine.LNX.4.58.0401271559230.10794@home.osdl.org>
2004-01-29 23:10           ` Fw: [PATCH][2.6] PCI Scan all functions Jake Moilanen
2004-01-29 23:30             ` Andrew Morton
2004-01-30 14:10               ` Jake Moilanen [this message]

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=1075471807.679.178.camel@magik \
    --to=moilanen@austin.ibm.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@lists.linuxppc.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.