Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: "Bradley D. LaRonde" <brad@ltc.com>
Cc: linux-mips@oss.sgi.com, linux-mips-kernel@lists.sourceforge.net
Subject: Re: PATCH: pci_auto bridge support
Date: Mon, 29 Oct 2001 14:38:50 -0800	[thread overview]
Message-ID: <3BDDDA7A.329F827D@mvista.com> (raw)
In-Reply-To: 04c801c160b0$1d62f660$3501010a@ltc.com

"Bradley D. LaRonde" wrote:
> 
> I considered that, but since only this small chuck of run-once surrogate
> bios autoconfig code needs to know, I figured better keep it separate.
> 

I would vote to put it inside the hose structure:

. It makes a workaround look like a real fix. :-)

. In other implementations of pci_auto, hose is the private sys data of a pci
dev. Having a bus number inside is very useful (e.g., pci_ops can tell whether
it is type0 of type1 configuration based on the bus number rather than a shaky
NULL parent bus pointer).  In the future, all pci_auto should be combined into
the pci driver.  So that is probably the right direction to go.

I think hose may evolve to be the data structure that represents the topology
of PCI buses.  It should have more uses in the future (e.g., the standard IRQ
routing across PCI-PCI bridges).


Jun

> 
> ----- Original Message -----
> From: "Jun Sun" <jsun@mvista.com>
> To: "Bradley D. LaRonde" <brad@ltc.com>
> Cc: <linux-mips@oss.sgi.com>; <linux-mips-kernel@lists.sourceforge.net>
> Sent: Monday, October 29, 2001 2:24 PM
> Subject: Re: PATCH: pci_auto bridge support
> 
> >
> > Brad,
> >
> > Have you considered embedding "topbus" argument into hose structure?  That
> > sounds like potentially better solution.
> >
> >
> >
> > "Bradley D. LaRonde" wrote:
> > >
> > > 2001-10-26  Bradley D. LaRonde <brad@ltc.com>
> > >
> > > * PCI bridge support.  See change log entry below.
> > >
> > > --- arch/mips/kernel/pci_auto.c 2001/08/18 06:21:53     1.1
> > > +++ arch/mips/kernel/pci_auto.c 2001/10/27 01:01:21
> > > @@ -4,6 +4,7 @@
> > >   * Author: Matt Porter <mporter@mvista.com>
> > >   *
> > >   * Copyright 2000, 2001 MontaVista Software Inc.
> > > + * Copyright 2001 Bradley D. LaRonde <brad@ltc.com>
> > >   *
> > >   * This program is free software; you can redistribute  it and/or
> modify it
> > >   * under  the terms of  the GNU General  Public License as published by
> the
> > > @@ -19,6 +20,15 @@
> > >   * . change most int to u32.
> > >   *
> > >   * Further modified to include it as mips generic code,
> ppopov@mvista.com.
> > > + *
> > > + * 2001-10-26  Bradley D. LaRonde <brad@ltc.com>
> > > + * - Add a top_bus argument to the "early config" functions so that
> > > + *   they can set a fake parent bus pointer to convince the underlying
> > > + *   pci ops to use type 1 configuration for sub busses.
> > > + * - Set bridge base and limit registers correctly.
> > > + * - Align io and memory base properly before and after bridge setup.
> > > + * - Don't fall through to pci_setup_bars for bridge.
> > > + * - Reformat the debug output to look more like lspci's output.
> > >   */

  parent reply	other threads:[~2001-10-29 22:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-27  1:07 PATCH: pci_auto bridge support Bradley D. LaRonde
2001-10-29 19:24 ` Jun Sun
2001-10-29 19:30   ` Bradley D. LaRonde
2001-10-29 19:30     ` Bradley D. LaRonde
2001-10-29 22:38     ` Jun Sun [this message]
2001-10-30  0:00       ` [Linux-mips-kernel]Re: " Bradley D. LaRonde
2001-10-30  0:00         ` Bradley D. LaRonde
2001-10-30  0:19         ` Jun Sun

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=3BDDDA7A.329F827D@mvista.com \
    --to=jsun@mvista.com \
    --cc=brad@ltc.com \
    --cc=linux-mips-kernel@lists.sourceforge.net \
    --cc=linux-mips@oss.sgi.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