public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gérard Roudier" <groudier@club-internet.fr>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Todd Inglett <tinglett@vnet.ibm.com>,
	"David S. Miller" <davem@redhat.com>,
	<tgall%rchland.vnet@RCHGATE.RCHLAND.IBM.COM>,
	<linux-kernel@vger.kernel.org>
Subject: Re: RFC: Changes for PCI
Date: Thu, 28 Jun 2001 23:54:41 +0200 (CEST)	[thread overview]
Message-ID: <20010628234710.D1618-100000@> (raw)
In-Reply-To: <E15FfAV-0007GV-00@the-village.bc.nu>



On Thu, 28 Jun 2001, Alan Cox wrote:

> > beyond 256 physical busses in 2.4?  Maybe not.  But it is a simple
> > change and it does work and it works around the existing drivers which
> > compare busid+devfn for uniqueness when they really should compare
> > pci_dev pointers.  Should it be redone the correct way (domains) in
>
> I think it might be better to fix the needed drivers. I suspect ppc64 isnt
> going to need that man drivers handle with initially

As far as the Symbios driver is in concern, there is nothing to fix.

1) The bogus double reporting of PCI devices used (uses) 2 different
pci_dev structures.

2) The boot order has nothing to do with the kernel and must use the only
relevant way to identify PCI devices in a PCI BUS hierarchy (bus + devfn).

> > The patch does not handle the user mode case.  This leaves the X server
> > broken.  We could probably weed out busses beyond 256 under
> > /proc/bus/pci as a workaround -- meaning the video adapter (if any --
> > rare in these boxes) must be in one of the first I/O drawers.
>
> Or scan the busses for video cards and number those busses 0,1,2... then
> number the rest. Ugly but probably best for 2.4

Btw, the suggested PCI bus numbering change looks like utter hackery to
me... Seems some guys somewhere are abusing tequilla too much. :-)

  Gérard.


  reply	other threads:[~2001-06-28 21:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-27 22:06 RFC: Changes for PCI 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-28  1:02     ` David S. Miller
2001-06-27 19:07       ` Tom Gall
2001-06-29  5:22         ` Richard Henderson
2001-06-29  3:14           ` Tom Gall
2001-06-27 23:17   ` anton
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
     [not found]   ` <mailman.993682861.9307.linux-kernel2news@redhat.com>
2001-06-27 23:41     ` Pete Zaitcev
2001-06-28  0:48       ` David S. Miller
2001-06-28  1:00   ` David S. Miller
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
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=20010628234710.D1618-100000@ \
    --to=groudier@club-internet.fr \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tgall%rchland.vnet@RCHGATE.RCHLAND.IBM.COM \
    --cc=tinglett@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