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


anton@samba.org writes:
 > > Why not use sysdata like the other arches?
 > > 
 > > Changing the meaning of dev->bus->number globally seems pointless.  If
 > > you are going to do that, just do it the right way and introduce another
 > > struct member, pci_domain or somesuch.
 > 
 > Thats 2.5 material. For 2.4 we should do as davem suggested and make
 > the bus number unique. I do this by just adding 256 to each overlapping
 > host bridge.

Looks, ppc64 is really still experimental right?  Which means it is
2.5.x material, and 2.5.x has been quoted as being a week or two away.

So we can solve this problem for real, with system bus domains, and
get ppc64 working all within the framework of 2.5.x which is just
around the corner.

For now, I am rather sure your systems for testing have < 256 physical
PCI busses and you can for 2.4.x use the remapping scheme sparc64 uses.

Later,
David S. Miller
davem@redhat.com

  parent reply	other threads:[~2001-06-28  1:05 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
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 [this message]
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.33445.396761.71174@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=anton@samba.org \
    --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®