From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: Little script for ISAPNP hotplug
Date: Mon, 12 Apr 2004 02:25:32 +0000 [thread overview]
Message-ID: <4079FE1C.6050101@ums.usu.ru> (raw)
In-Reply-To: <200404092044.54429.simone.gotti@email.it>
Simone Gotti wrote:
>Thanks to Alexander E. Patrakov that made a similar script, I've added his
>functions for the conversion of the string form to the ID form in the
>isapnp.rc script.
>
>
The script that you attached has no equivalent of my
simplify_isapnpmap_line() function and will thus fail if the line in
modules.isapnpmap contains multiple vendor/function pairs and the second
one (not the first one) matches
The line in modules.isapnpmap is:
# module cardvendor carddevice driver_data vendor function [vendor2 function2] ...
\--------"the rest"-------------------/
The simplify_isapnpmap_line() function expects the $module,
$cardvendor and $carddevice variables to be set, driver_data
ignored, and "the rest" to be the arguments. It outputs
lines of the following form:
# module cardvendor carddevice vendor function
# module cardvendor carddevice vendor2 function2
to match against.
Or do you just ignore the "vendor" and "function" fields? This is
dangerous, since there are lines with 0xffff as both carddevice
and cardvendor.
Also, your script outputs:
/proc/bus/pnp/ or /proc/bus/isapnp/ not found, Is it enabled in your kernel?
if the support is compiled into the kernel, but there are no isapnp devices
in the system.
--
Alexander E. Patrakov
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-04-12 2:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 18:44 Little script for ISAPNP hotplug Simone Gotti
2004-04-10 17:16 ` Simone Gotti
2004-04-11 17:09 ` Simone Gotti
2004-04-12 2:25 ` Alexander E. Patrakov [this message]
2004-04-12 9:57 ` Simone Gotti
2004-04-13 15:47 ` Alexander E. Patrakov
2004-04-13 17:06 ` Simone Gotti
2004-04-18 19:10 ` Simone Gotti
2004-04-22 18:14 ` Simone Gotti
2004-04-22 19:28 ` Marco d'Itri
2004-04-23 9:42 ` Simone Gotti
2004-04-23 16:19 ` Bill Nottingham
2004-04-23 16:23 ` Marco d'Itri
2004-04-23 16:30 ` Bill Nottingham
2004-04-24 9:15 ` Simone Gotti
2004-04-24 9:15 ` Simone Gotti
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=4079FE1C.6050101@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).