[lkml]   [2003]   [Mar]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2.5] Make root PCI bus child of system_bus in device tree

On Tue, 25 Mar 2003, Deepak Saxena wrote:

> On Mar 26 2003, at 00:35, Alan Cox was caught saying:
> > On Tue, 2003-03-25 at 23:16, Deepak Saxena wrote:
> > > All,
> > >
> > > The following patch updates the PCI subsystem so that root PCI host
> > > bridges appear as devices hanging off the system bus instead of root
> >
> > This seems odd for some systems we support. Older PARISC for example
> > have PCI busses hanging off gecko. I do agree with you for the general
> > case. So systems whose root level bridges are 'normal' should reflect
> > this and I guess others should attach them to the relevant bus.
> >
> > Over time it seems that PCI is going to become a secondary bus like
> > ISA did as well. In fact it already has in many ways, its just things
> > like VLINK and the Intel hub busses look like PCI to us
> Sounds like more reasoning to just force the caller to provide a parent.
> 'normal' is a moving target and I'd rather not have the code making
> assumptions and let the platform's kernel developer explictly map
> the PCI bridge into the system.

Actually, that's been the intention all along. The PCI code may not
support it today (I haven't looked at it in a while), but there is no
reason why the parent for a host bridge couldn't be set, and the bridge
show up in the proper place in the hierarchy.

And, if it isn't set, then it shows up under the root, which makes sense
physically and conceptually.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:34    [W:0.020 / U:1.172 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site