public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: PCI question
Date: Tue, 03 Feb 2004 22:56:55 +0000	[thread overview]
Message-ID: <20040203225655.GU18725@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200402032235.i13MZQXl018906@fsgi900.americas.sgi.com>

On Tue, Feb 03, 2004 at 04:35:26PM -0600, Pat Gefre wrote:
> The usage of pci_dev.sysdata is a bit confusing to me. I had initially
> thought that this was available for any system specific use,  but then
> in pcibios_fixup_device_resources() it is specifically cast as a struct
> pci_controller *:

It's up to the architecture how it's used.  ia64 has decided that it
shall be a struct pci_controller *.

> In this funtion  the pci_controller elements 'window[]' and 'windows'
> are also used.  This implies to me that these fields must be maintained
> in any system specific structure ? i.e.
> 
> struct my_sysdata_struct {
>    struct pci_controller dummy;
>    /* my stuff would go here */
>    struct my_real_sysdata_stuff;
> };
> 
> Yet I don't see where anyone else is doing the above. Am I missing
> something obvious ??

Urgh, don't do that.  What do you need to do that can't be added to the
pci_controller?

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

  reply	other threads:[~2004-02-03 22:56 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 [this message]
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
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=20040203225655.GU18725@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --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