mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Deepak Saxena <dsaxena@mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dsaxena@mvista.com, mochel@osdl.org,
	Linus Torvalds <torvalds@transmeta.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.5] Make root PCI bus child of system_bus in device tree
Date: Tue, 25 Mar 2003 16:31:18 -0700	[thread overview]
Message-ID: <20030325233118.GA16920@xanadu.az.mvista.com> (raw)
In-Reply-To: <1048638924.29988.21.camel@irongate.swansea.linux.org.uk>

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.

~Deepak

-- 
Deepak Saxena
MontaVista Software - Powering the Embedded Revolution - www.mvista.com


  reply	other threads:[~2003-03-25 23:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25 23:16 Deepak Saxena
2003-03-26  0:35 ` Alan Cox
2003-03-25 23:31   ` Deepak Saxena [this message]
2003-03-25 22:40     ` Patrick Mochel

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=20030325233118.GA16920@xanadu.az.mvista.com \
    --to=dsaxena@mvista.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=torvalds@transmeta.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®