From: Greg KH <greg@kroah.com>
To: Scott Murray <scottm@somanetworks.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
KOCHI Takayoshi <t-kouchi@mvf.biglobe.ne.jp>,
jung-ik.lee@intel.com, tony.luck@intel.com,
pcihpd-discuss@lists.sourceforge.net, linux-ia64@linuxia64.org,
linux-kernel@vger.kernel.org
Subject: Re: [Pcihpd-discuss] Re: PCI Hotplug Drivers for 2.5
Date: Thu, 24 Oct 2002 14:49:52 -0700 [thread overview]
Message-ID: <20021024214952.GK25159@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0210241300220.10937-100000@rancor.yyz.somanetworks.com>
On Thu, Oct 24, 2002 at 01:44:06PM -0400, Scott Murray wrote:
>
> I don't know if you looked at my cPCI driver patch in detail, but it uses
> the setup-*.c code for all of its resource management.
I'm sorry, but I only glanced at it and missed this point.
> The only things that were really missing in 2.4.x were:
>
> - exports of a few things, most notably pci_scan_bridge
> - code to update the resource windows of a newly added bridge (recursively)
> - a pci_write_bridge_bases
> - PCI resource reservation to allow hot insertion on dumb cPCI hardware
> - on x86, the smarts to work back to the root PCI bus to figure out the
> IRQ pin to use when looking in the pirq table
All of these seem like things that should belong in the setup-*.c files
for others to use.
> Since I've been swamped with other stuff, I just started finally porting
> my cPCI stuff to 2.5 yesterday. :( I think I can get it up and running
> relatively quickly, but figuring out Ivan's newer hotplug helper code
> and how to take advantage of it might take me a couple of days.
Nice, I was wondering what happened. I'll go dig up your older patch
and take a closer look at it.
thanks,
greg k-h
next prev parent reply other threads:[~2002-10-24 21:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 4:33 PCI Hotplug Drivers for 2.5 Lee, Jung-Ik
2002-10-24 5:10 ` Greg KH
2002-10-24 5:59 ` KOCHI, Takayoshi
2002-10-24 6:12 ` Greg KH
2002-10-24 11:49 ` [Linux-ia64] " Matthew Wilcox
2002-10-24 14:52 ` Jeff Garzik
2002-10-24 16:54 ` Greg KH
2002-10-24 17:44 ` [Pcihpd-discuss] " Scott Murray
2002-10-24 21:49 ` Greg KH [this message]
2002-10-24 22:22 ` Scott Murray
2002-10-25 15:37 ` Ivan Kokshaysky
2002-10-25 22:02 ` Scott Murray
2002-10-25 22:25 ` Russell King
2002-10-26 23:36 ` Scott Murray
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=20021024214952.GK25159@kroah.com \
--to=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=jung-ik.lee@intel.com \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=scottm@somanetworks.com \
--cc=t-kouchi@mvf.biglobe.ne.jp \
--cc=tony.luck@intel.com \
/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.