From: Simone Gotti <simone.gotti@email.it>
To: linux-hotplug@vger.kernel.org
Subject: Re: Little script for ISAPNP hotplug
Date: Tue, 13 Apr 2004 17:06:14 +0000 [thread overview]
Message-ID: <200404131906.14454.simone.gotti@email.it> (raw)
In-Reply-To: <200404092044.54429.simone.gotti@email.it>
On Tuesday 13 April 2004 17:47, Alexander E. Patrakov wrote:
> Simone Gotti wrote:
> >No I'm using the vendor and function values but I didn't know that there
> > can be more the 1 value of vendor and function for every line of
> >modules.isapnpmap. Now I've changed the script, it's attached.
>
> I see the change in isapnp.agent. It is probably still wrong: I don't
> see the equivalent of the following lines:
>
> rawvendor=`echo $ID | cut -b8-10`
> rawfunction=`echo $ID | cut -b11-14`
>
This is the contents of my /proc/bus/pnp/devices. It's for 2.6 kernels (I
don't use 2.4 anymore). I think that probably it's quite different from the
2.4 version. For this reason I have used a different parsing function.
I have to try a 2.4 kernel but like I've said in the last compiled I can't
found the /proc/bus/isapnp directory...
In 2.6 like you can see in isapnp.rc I prefer the use of sysfs.
# cat /proc/bus/pnp/devices
00 0000d041 08:00:00 0003
01 0002d041 08:01:00 0003
02 0001d041 08:02:01 0003
03 000bd041 08:03:00 0003
04 0303d041 09:00:00 000b
05 0008d041 08:80:00 0003
06 040cd041 0b:01:00 0003
07 010cd041 05:00:00 0003
08 020cd041 08:80:00 0003
09 030ad041 06:04:00 0003
0a 130fd041 09:02:00 0180
0b 020cd041 08:80:00 0003
0c 0105d041 07:00:02 0180
0d 0007d041 01:02:00 0003
0e 0004d041 07:01:00 0180
10 0105d041 07:00:02 0180
11 06b0d041 04:01:00 0180
12 2fb0d041 04:01:00 0180
> Also, I don't see any attempt to follow "0xffff matches everything" rule.
I didn't know that this was a rule. If you say that it's mandatory to check
for this I'll do it!
Thanks!
Bye!
--
Simone Gotti
<simone.gotti@email.it>
-------------------------------------------------------
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-13 17:06 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
2004-04-12 9:57 ` Simone Gotti
2004-04-13 15:47 ` Alexander E. Patrakov
2004-04-13 17:06 ` Simone Gotti [this message]
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=200404131906.14454.simone.gotti@email.it \
--to=simone.gotti@email.it \
--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).