public inbox for linux-kernel@vger.kernel.org
 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
Date: Tue, 25 Sep 2001 13:32:34 -0700	[thread overview]
Message-ID: <20010925133234.A14610@kroah.com> (raw)

Hi,

Another release of the Compaq Hotplug PCI driver is available against
2.4.10 is at:
	http://www.kroah.com/linux/hotplug/pci-hotplug-2001_09_25-2.4.10.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
	- added MODULE_LICENSE("GPL") to the modules.
	- fixed 64 bit problems in the hotplug_pci core (thanks to Arjan
	  van de Ven for pointing this out to me)
	- changed the hotplug pci core interface from a controller based
	  interface to a physical slot based one.
	- modified the Compaq driver to match the new hotplug pci core
	  changes.
	- code documentation updates.
        - added MODULE support to the hotplug_pci core to prevent a
          a child module from disappearing while it is being called.
	- no more oops if the hotplug_slot_ops structure is missing a
	  field.

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

Note:  This is probably the LAST release of this driver that the Compaq
user interface tools will work on.  If you care about compatiblity with
these tools, please grab this release and keep it :)  Also, please let
me know if you have a problem with this.

TODO:
	- move the /proc/cpqphpd code out of the compaq driver and into
	  the hotplug_pci core code.
	- change the /proc/cpqphpd interface into a real filesystem.
	- either remove the Compaq BIOS specific code or fix it to not
	  use direct memory accesses (any opinions?)

thanks,

greg k-h

                 reply	other threads:[~2001-09-25 20:36 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=20010925133234.A14610@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