public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	"Albert D. Cahalan" <acahalan@cs.uml.edu>,
	Tom Gall <tom_gall@vnet.ibm.com>
Subject: Re: Going beyond 256 PCI buses
Date: Thu, 14 Jun 2001 16:08:24 -0400	[thread overview]
Message-ID: <3B2919B8.85D38801@mandrakesoft.com> (raw)
In-Reply-To: <15145.1739.395626.842663@pizda.ninka.net> <200106141904.f5EJ4AD413350@saturn.cs.uml.edu> <15145.3254.105970.424506@pizda.ninka.net> <3B29137B.CA8442B8@mandrakesoft.com> <15145.5939.879723.656331@pizda.ninka.net>

"David S. Miller" wrote:
> 
> Jeff Garzik writes:
>  > Thinking a bit more independently of bus type, and with an eye toward's
>  > 2.5's s/pci_dev/device/ and s/pci_driver/driver/, would it be useful to
>  > go ahead and codify the concept of PCI domains into a more generic
>  > concept of bus tree numbers?  (or something along those lines)  That
>  > would allow for a more general picture of the entire system's device
>  > tree, across buses.
>  >
>  > First sbus bus is tree-0, first PCI bus tree is tree-1, second PCI bus
>  > tree is tree-2, ...
> 
> If you're going to do something like this, ie. true hierarchy, why not
> make one tree which is "system", right? Use /proc/bus/${controllernum}
> ala:
> 
> /proc/bus/0/type        --> "sbus", "pci", "zorro", etc.
> /proc/bus/0/*           --> for type == "pci" ${bus}/${dev}.${fn}
>                             for type == "sbus" ${slot}
>                             ...
> 
> How about this?

ok with me.  would bus #0 be the system or root bus?  that would be my
preference, in a tiered system like this.

-- 
Jeff Garzik      | Andre the Giant has a posse.
Building 1024    |
MandrakeSoft     |

  reply	other threads:[~2001-06-14 20:08 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 10:02 Going beyond 256 PCI buses Tom Gall
2001-06-13 17:17 ` Albert D. Cahalan
2001-06-13 18:29   ` Tom Gall
2001-06-14 14:14 ` Jeff Garzik
2001-06-14 14:24   ` David S. Miller
2001-06-14 14:32     ` Jeff Garzik
2001-06-14 14:42       ` David S. Miller
2001-06-14 15:29         ` Jeff Garzik
2001-06-14 15:33           ` Jeff Garzik
2001-06-14 17:59     ` Jonathan Lundell
2001-06-14 19:03       ` David S. Miller
2001-06-14 20:50         ` Jonathan Lundell
2001-06-14 20:56           ` David S. Miller
2001-06-14 18:01     ` Albert D. Cahalan
2001-06-14 18:47       ` David S. Miller
2001-06-14 19:04         ` Albert D. Cahalan
2001-06-14 19:12           ` David S. Miller
2001-06-14 19:41             ` Jeff Garzik
2001-06-14 19:57               ` David S. Miller
2001-06-14 20:08                 ` Jeff Garzik [this message]
2001-06-14 20:14                   ` David S. Miller
2001-06-14 21:30                     ` Benjamin Herrenschmidt
2001-06-14 21:35                       ` David S. Miller
2001-06-14 21:46                         ` Benjamin Herrenschmidt
2001-06-14 21:46                       ` Jeff Garzik
2001-06-14 21:48                         ` David S. Miller
2001-06-14 21:57                           ` Benjamin Herrenschmidt
2001-06-14 22:12                             ` David S. Miller
2001-06-14 22:29                               ` Benjamin Herrenschmidt
2001-06-14 22:49                                 ` David S. Miller
2001-06-14 23:35                                   ` Benjamin Herrenschmidt
2001-06-14 23:35                               ` VGA handling was [Re: Going beyond 256 PCI buses] James Simmons
2001-06-14 23:42                                 ` David S. Miller
2001-06-14 23:55                                   ` James Simmons
2001-06-15 15:14                                     ` Pavel Machek
2001-06-15  2:06                                   ` Albert D. Cahalan
2001-06-15  8:52                                   ` Matan Ziv-Av
2001-06-16 21:32                     ` Going beyond 256 PCI buses Jeff Garzik
2001-06-16 23:29                       ` Benjamin Herrenschmidt
2001-06-15  8:42             ` Geert Uytterhoeven
2001-06-15 15:38               ` David S. Miller
2001-06-14 15:13   ` Jonathan Lundell
2001-06-14 15:15     ` David S. Miller
2001-06-14 15:17     ` 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=3B2919B8.85D38801@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=acahalan@cs.uml.edu \
    --cc=davem@redhat.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