public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: PCI question
Date: Wed, 04 Feb 2004 03:28:56 +0000	[thread overview]
Message-ID: <20040204032856.GC11566@sgi.com> (raw)
In-Reply-To: <200402032235.i13MZQXl018906@fsgi900.americas.sgi.com>

On Tue, Feb 03, 2004 at 05:36:53PM -0600, Patrick Gefre wrote:
> But not in 2.6 ??
> 
> struct pci_controller {
>        void *acpi_handle;
>        void *iommu;
>        int segment;
> 
>        unsigned int windows;
>        struct pci_window *window;
> };

Oops, I was looking at a 2.4 tree.  I wonder if we can overload
acpi_handle for our purposes though?  Since we don't have an ACPI
namespace, we obviously don't store things like the bridge base address
and PIO mapping information there, so we may be able to make this field
point to an sn2 specific structure that contains this info (I'm assuming
that's what we need).

What else do we need to keep track of?  The PCI to node mapping should
be stored seperately (I think mkp had a patch to implement that), but
I'm sure there are other things I'm missing...

Thanks,
Jesse

  parent reply	other threads:[~2004-02-04  3:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03 22:35 PCI question Pat Gefre
2004-02-03 22:56 ` Matthew Wilcox
2004-02-03 23:15 ` Patrick Gefre
2004-02-03 23:29 ` Jesse Barnes
2004-02-03 23:36 ` Patrick Gefre
2004-02-04  3:28 ` Jesse Barnes [this message]
2004-02-04 17:04 ` Patrick Gefre
2004-02-04 17:48 ` Grant Grundler
2004-02-04 19:10 ` Patrick Gefre
2004-02-04 19:50 ` Bjorn Helgaas
2004-02-05 17:11 ` Patrick Gefre

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=20040204032856.GC11566@sgi.com \
    --to=jbarnes@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    /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