mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: tom_gall@vnet.ibm.com
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>, linux-kernel@vger.kernel.org
Subject: Re: RFC: Changes for PCI
Date: Wed, 27 Jun 2001 18:02:44 -0700 (PDT)	[thread overview]
Message-ID: <15162.33332.781686.45753@pizda.ninka.net> (raw)
In-Reply-To: <3B3A64CD.28B72A2A@vnet.ibm.com>
In-Reply-To: <3B3A58FC.2728DAFF@vnet.ibm.com> <3B3A5B00.9FF387C9@mandrakesoft.com> <3B3A64CD.28B72A2A@vnet.ibm.com>


Tom Gall writes:
 > Well you have device drivers like the symbios scsi driver for instance that
 > tries to determine if it's seen a card before. It does this by looking at the
 > bus,dev etc numbers...  It's quite reasonable for two different scsi cards to be
 > on the same bus number, same dev number etc yet they are in different PCI
 > domains.
 > 
 > Is this a device driver bug or feature?

As Peter Zaitcev and others have pointed out, they can use simple
pointer comparisons here on the pci_dev struct.

 > Right, one could do that and then all the large machine architectures would have
 > their own implementation for the same problem. That's not necessarily a bad
 > thing, but some commonality I think would be a good thing.

Well, if the claim is that your suggested changes provide this
"commonality", I totally disagree.  Your changes do no more than
provide hooks where no hooks are needed.  The hooks are there,
and are why we have "sysdata" and all the drivers/pci/setup-*.c
buisness.  If ppc64 cannot fit itself into the drivers/pci/setup-*.c
infrastructure, either fix the infrastructure or concede that "our
stuff is too weird to solve with generic code" and do what sparc64
does with driving it's own PCI probing layer.

Later,
David S. Miller
davem@redhat.com

  parent reply	other threads:[~2001-06-28  1:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.993682861.9307.linux-kernel2news@redhat.com>
2001-06-27 22:06 ` Tom Gall
2001-06-27 22:15   ` Jeff Garzik
2001-06-27 22:57     ` Tom Gall
2001-06-27 23:34       ` Jeff Garzik
2001-06-27 18:24         ` Tom Gall
2001-06-28 20:57         ` Gérard Roudier
2001-06-28 21:11           ` Tom Gall
2001-06-28 21:18             ` Jeff Garzik
2001-06-28 21:12           ` Jeff Garzik
2001-06-27 23:17     ` anton
2001-06-27 23:41     ` Pete Zaitcev
2001-06-28  1:02     ` David S. Miller [this message]
2001-06-27 19:07       ` Tom Gall
2001-06-29  5:22         ` Richard Henderson
2001-06-29  3:14           ` Tom Gall
2001-06-28  1:04     ` David S. Miller
2001-06-27 18:49       ` Tom Gall
2001-06-28  4:06       ` David S. Miller
2001-06-27 20:01         ` Tom Gall
2001-06-27 23:12   ` anton
2001-06-28  0:59   ` David S. Miller
2001-06-28 16:48     ` Todd Inglett
2001-06-28 17:01       ` Jeff Garzik
2001-06-28 17:20         ` Todd Inglett
2001-06-28 17:01       ` Alan Cox
2001-06-28 21:54         ` Gérard Roudier
2001-06-28  1:00   ` David S. Miller
2001-06-28  0:48 ` David S. Miller
2001-06-28 23:08 Khachaturov, Vassilii
2001-06-28 23:27 ` Jeff Garzik

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=15162.33332.781686.45753@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom_gall@vnet.ibm.com \
    /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®