All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: [Pcihpd-discuss] PCI hotplug broken on IA64
Date: Thu, 31 Oct 2002 05:52:44 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805304@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805303@msgid-missing>

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 :)

thanks,

greg k-h


  reply	other threads:[~2002-10-31  5:52 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 ` Greg KH [this message]
2002-10-31  5:58 ` [Linux-ia64] " Greg KH
2002-10-31  6:00 ` Greg KH
2002-10-31  6:55 ` [Linux-ia64] " Lee, Jung-Ik
2002-10-31  7:40 ` [Linux-ia64] " 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-105590709805304@msgid-missing \
    --to=greg@kroah.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.