All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zink, Dan" <Dan.Zink@COMPAQ.com>
To: linux-hotplug@vger.kernel.org
Subject: PATCH: pci.agent script fixup
Date: Wed, 17 Jan 2001 16:48:48 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-97974994811347@msgid-missing> (raw)

I tracked down the problems with the pci.agent script.  Here's
the patch:


diff -Nuar etc/hotplug/pci.agent /etc/hotplug/pci.agent
--- etc/hotplug/pci.agent	Wed Jan 17 00:35:33 2001
+++ /etc/hotplug/pci.agent	Wed Jan 17 10:29:23 2001
@@ -28,9 +28,10 @@
 #
 # $Id: pci.agent,v 1.2 2001/01/17 00:53:18 dbrownell Exp $
 #
+. hotplug.functions
 
 # generated by modutils, for current 2.4.x kernels
-PCI_MAP=$MODULE_DIR/modules.pcimap
+MAP_CURRENT=$MODULE_DIR/modules.pcimap
 
 # accumulates list of modules we may care about
 DRIVERS@@ -62,12 +63,12 @@
 	exit 1
     fi
 
-    XID=`echo $PCI_ID | $AWK -F/ '{print "0x" $1, "0x" $2 }'`
+    XID=`echo $PCI_ID | $AWK -F: '{print "0x" $1, "0x" $2 }'`
     read pci_class pci_id_vendor pci_id_device << EOT
 0x$PCI_CLASS $XID
 EOT
 
-    XID=`echo $PCI_SUBSYS_ID | $AWK -F/ '{print "0x" $1, "0x" $2 }'`
+    XID=`echo $PCI_SUBSYS_ID | $AWK -F: '{print "0x" $1, "0x" $2 }'`
     read pci_subid_vendor pci_subid_device << EOT
 $XID
 EOT
@@ -138,7 +139,7 @@
 
     # on 2.4 systems, modutils maintains MAP_CURRENT
     if [ -r $MAP_CURRENT ]; then
-    	load_drivers usb $MAP_CURRENT "$LABEL"
+    	load_drivers pci $MAP_CURRENT "$LABEL"
     fi
 
     if [ "$DRIVERS" = "" ]; then



____________________________
dan.zink@compaq.com


_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2001-01-17 16:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-17 16:48 Zink, Dan [this message]
2001-01-17 17:12 ` PATCH: pci.agent script fixup David Brownell

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-hotplug-97974994811347@msgid-missing \
    --to=dan.zink@compaq.com \
    --cc=linux-hotplug@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.