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: Wed, 04 Feb 2004 19:10:46 +0000	[thread overview]
Message-ID: <402143B6.1040205@sgi.com> (raw)
In-Reply-To: <200402032235.i13MZQXl018906@fsgi900.americas.sgi.com>

Grant Grundler wrote:

>On Wed, Feb 04, 2004 at 11:04:42AM -0600, Patrick Gefre wrote:
>  
>
>>I think the 2.4 definition will be fine - at least for now. Was there a 
>>reason it was changed in 2.6 ?
>>    
>>
>
>Because no one was using it?
>
>Pat,
>two (three?) people have asked you to state what you want to add.
>Can you state the basic problem additional data fields would solve?
>
>It might be easier to just add those fields directly to pci_controller
>instead of messing with platform_data.
>
>grant
>  
>
We keep track of several things that are specific to our system:

struct sn_device_sysdata {
        vertex_hdl_t            vhdl;
        pciio_provider_t        *pci_provider;
        pciio_intr_t            intr_handle;
        struct sn_flush_device_list *dma_flush_list;
        pciio_piomap_t          pio_map[PCI_ROM_RESOURCE];
};

The platform_data element is what we use in 2.4 and seems like the way 
to go for 2.6.

-- Pat


  parent reply	other threads:[~2004-02-04 19:10 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
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 [this message]
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=402143B6.1040205@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.