From: Patrick Gefre <pfg@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: PCI question
Date: Thu, 05 Feb 2004 17:11:09 +0000 [thread overview]
Message-ID: <4022792D.2070309@sgi.com> (raw)
In-Reply-To: <200402032235.i13MZQXl018906@fsgi900.americas.sgi.com>
Greg KH wrote:
>On Tue, Feb 03, 2004 at 04:27:09PM -0600, Patrick 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 *:
>>
>>#define PCI_CONTROLLER(busdev) ((struct pci_controller *) busdev->sysdata)
>>
>>void __init
>>pcibios_fixup_device_resources (struct pci_dev *dev, struct pci_bus *bus)
>>
>>
>
>What kernel are you looking at? I don't see either of the above in the
>2.6.2 kernel tree.
>
>thanks,
>
>greg k-h
>
>
In my bitkeeper tree : (bk parent: http://linux.bkbits.net/linux-2.5)
include/asm-ia64/pci.h:
#define PCI_CONTROLLER(busdev) ((struct pci_controller *) busdev->sysdata)
arch/ia64/pci/pci.c:
void __init
pcibios_fixup_device_resources (struct pci_dev *dev, struct pci_bus *bus)
Is there some ia64 patch I'm missing that removes this ?
-- Pat
prev parent reply other threads:[~2004-02-05 17:11 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
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 [this message]
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=4022792D.2070309@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox