public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lee, Jung-Ik" <jung-ik.lee@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] RE: [Pcihpd-discuss] PCI hotplug broken on IA64
Date: Thu, 31 Oct 2002 06:55:12 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805307@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805303@msgid-missing>

> On Wed, Oct 30, 2002 at 09:52:44PM -0800, Greg KH wrote:
> > On Wed, Oct 30, 2002 at 08:49:24PM -0800, Lee, Jung-Ik wrote:
> > > 
> > > > I don't think the current way of accessing PCI 
> configuration space
> > > > with temporary pci_dev and pci_bus is definitive answer but we
> > > > are depending on it now.
> > > > Could someone enlighten me?
> > > > Any ideas?
> > > 
> > > All pci config space access before pci_dev/pci_bus are built
> > > should be able to make direct call to
> > > pci_config_{read|write}(seg, bus, dev, func, offset, size, value).
> > 
> > Um, where are these functions exported?  I don't see them in the 2.4
> > tree :)
> 
> Ok, just to make myself clear, yes I know the functions are there, but
> no, they are not explicitly exported, or supported on all archs.
> 

Hotplug drivers in drivers/hotplug are for Intel architecture,
and the above APIs are available as global for both i386 and ia64.
Actually, acpi driver uses them for ACPI/PCI population before 
pci_dev is built for the hierarchy.

thanks,
J.I.




  parent reply	other threads:[~2002-10-31  6:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31  4:49 [Linux-ia64] RE: [Pcihpd-discuss] PCI hotplug broken on IA64 Lee, Jung-Ik
2002-10-31  5:52 ` [Linux-ia64] " Greg KH
2002-10-31  5:58 ` Greg KH
2002-10-31  6:00 ` Greg KH
2002-10-31  6:55 ` Lee, Jung-Ik [this message]
2002-10-31  7:40 ` Greg KH
2002-10-31  8:03 ` Scott Murray
2002-10-31  8:19 ` Greg KH
2002-10-31  8:41 ` Scott Murray
2002-10-31 12:27 ` Matthew Wilcox

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=marc-linux-ia64-105590709805307@msgid-missing \
    --to=jung-ik.lee@intel.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