mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] Hotplug PCI driver for 2.4.10-pre10
Date: Mon, 17 Sep 2001 16:25:38 -0700	[thread overview]
Message-ID: <20010917162538.A1090@kroah.com> (raw)

Hi,

Another release of the Compaq Hotplug PCI driver is available against
2.4.10-pre10 is at:
	http://www.kroah.com/linux/hotplug/pci-hotplug-2001_09_17-2.4.10-pre10.patch.gz
With a full changelog at:
	http://www.kroah.com/linux/hotplug/pci-hotplug-Changelog

Changes since the last release:
 	- forward ported to 2.4.10-pre10
	- removed lots of dead code in the Compaq driver that was not
	  being used.
	- created pci_read_config_*_nodev and pci_write_config_*_nodev
	  that corresponds with the pci_read_config_* and
	  pci_write_config_* functions.  These functions can be used
	  when there is not a valid struct pci_dev available for the
	  device.  The functions will fallback to using the
	  pci_write_config_* and pci_read_config_* functions if a struct
	  pci_dev is found for the specified device.
	- enabled the hotplug_pci core to be compiled into the kernel.
	- added documentation to the hotplug_pci interface.

Again, the old Compaq tool will not work with this version of the
driver.  An updated version must be downloaded from the cvs tree at
sf.net at:
	http://sourceforge.net/cvs/?group_id=32538

I'm awaiting some comments from some people at IBM for what pieces of
the resource management code would be useful to have split out from the
Compaq driver.  Any comments from other groups who are working on
hotplug pci drivers is very welcome.

Next up is removing the horrid /proc interface the driver uses :)

thanks,

greg k-h

                 reply	other threads:[~2001-09-17 23:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010917162538.A1090@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®