mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: alan@lxorguk.ukuu.org.uk
Cc: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: Removal of pci_find_* in 2.5
Date: Fri, 12 Jul 2002 18:12:14 -0700 (PDT)	[thread overview]
Message-ID: <20020712.181214.15590856.davem@redhat.com> (raw)
In-Reply-To: <1026527009.9958.69.camel@irongate.swansea.linux.org.uk>

   From: Alan Cox <alan@lxorguk.ukuu.org.uk>
   Date: 13 Jul 2002 03:23:29 +0100
   
   I have several examples where the ordering of the PCI cards is critical
   to get stuff like boot device and primary controller detection right.
   pci_register_driver doesn't appear to have a good way to deal with this
   or have I missed something ?

Cards get registered in the order they appear on the bus, or at least
that is the way the algorithm worked the last time I looked.

Or, what other facility do you need?

  reply	other threads:[~2002-07-13  1:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-13  0:36 Greg KH
2002-07-13  2:23 ` Alan Cox
2002-07-13  1:12   ` David S. Miller [this message]
2002-07-13 14:46     ` Alan Cox
2002-07-13 20:52       ` David S. Miller
2002-07-13 13:45         ` Benjamin Herrenschmidt
2002-07-15  5:25           ` David S. Miller
2002-07-16  0:26             ` Greg KH
2002-07-14 20:07 ` Eric W. Biederman
2002-07-16  0:25   ` Greg KH
2002-07-16 10:56     ` Eric W. Biederman
2002-07-16 17:33       ` Patrick Mochel
2002-07-17 12:41         ` Eric W. Biederman
2002-07-13  4:04 Matt_Domsch
2002-07-13  4:41 ` Jeff Garzik
2002-07-13  5:09   ` Greg KH
2002-07-13 14:35   ` Alan Cox
2002-07-13 15:37     ` Jeff Garzik
2002-07-13 17:06       ` Alan Cox
2002-07-13 19:28         ` Jeff Garzik
2002-07-13 19:33           ` Jeff Garzik
2002-07-13 13:13 Matt_Domsch
2002-07-16 19:23 Matt_Domsch

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=20020712.181214.15590856.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®