All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Gefre <pfg@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: PCI question
Date: Tue, 03 Feb 2004 23:15:44 +0000	[thread overview]
Message-ID: <40202BA0.3070507@sgi.com> (raw)
In-Reply-To: <200402032235.i13MZQXl018906@fsgi900.americas.sgi.com>

Matthew Wilcox wrote:

>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?
>
>  
>
OK- good - thanks. Yes the other option is to add it to the 
pci_controller struct.

-- Pat



  parent reply	other threads:[~2004-02-03 23:15 UTC|newest]

Thread overview: 13+ 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2003-03-28 21:40 Cameron, Steve
2003-03-28  9:28 Stephen Cameron

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=40202BA0.3070507@sgi.com \
    --to=pfg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.