From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 14 Jun 2001 15:42:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 14 Jun 2001 15:41:58 -0400 Received: from panic.ohr.gatech.edu ([130.207.47.194]:25491 "HELO havoc.gtf.org") by vger.kernel.org with SMTP id ; Thu, 14 Jun 2001 15:41:51 -0400 Message-ID: <3B29137B.CA8442B8@mandrakesoft.com> Date: Thu, 14 Jun 2001 15:41:47 -0400 From: Jeff Garzik Organization: MandrakeSoft X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre3 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Cc: "David S. Miller" , "Albert D. Cahalan" , Tom Gall Subject: Re: Going beyond 256 PCI buses In-Reply-To: <15145.1739.395626.842663@pizda.ninka.net> <200106141904.f5EJ4AD413350@saturn.cs.uml.edu> <15145.3254.105970.424506@pizda.ninka.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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, ... -- Jeff Garzik | Andre the Giant has a posse. Building 1024 | MandrakeSoft |