Little script for ISAPNP hotplug

Little script for ISAPNP hotplug

[Simone Gotti]

Hi to all,

I was bored that hotplug wasn't able to load my isapnp device's modules.
Like the serial ports, parportpc, joystick port etc...

So I've written a little agent that do this work bacause I wasn't able to find 
a already done script.

I've did this script today in 3 hours and by now it can only manage the 
coldplug (I don't have any hotpluggable isa card but only the motherboard 
chips).   

It uses the contents of /proc/bus/pnp/devices bacause in sysfs it give the id 
in a string form (for example PNP0000) and I'm not able to convert them in 
the hex form with a bash script (I'm able to do this with a C program like 
lspnp do).

The other things is that this script must parse the contents of 
modules.isapnpmap because there isn't a program like usbmodules or 
pcimodules, so it slooow. 
If someone is interested I'll be happy to do a program like usbmodules.

My question is: Is there already a script like this? If not, does someone is 
interested in it and in the usbmodules like program?

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

Re: Little script for ISAPNP hotplug

[Simone Gotti]

[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]

On Friday 09 April 2004 20:44, Simone Gotti wrote:

By the way, today I've did the C modules.isapnp parser program.

The program is called "strange but true" isapnpmodules.
it's very simple, as I've used like base the code of usbmodules.

The scripts are 2 and a patch for hotplug.functions:

isapnp.rc 
isapnp.agent
hotplug.functions.patch (the patch is against hotplug-20040401, the latest 
avaible on my gentoo system) 

I've noticed that for the 2.6 kernel is prefered the bash parsing and not the 
use of usbmodules and pcimodules. 
The problem with isapnp is that in a standard PC there are more then 10 isa 
devices so in this way modules.isapnp is parsed a lot of times and all is 
slow (at least 16 seconds). 
Using the isapnpmodules it take not more than 2 seconds. So I've prefered it 
to bash parsing in the 2.6 kernel too.

I don't know it I've do something wrong due to my low level of documentation 
on how isapnp works.

isapnp.rc:
It checks if isapnp exists, then it look for the presence of sysfs. If both 
exists then sysfs data is used. This because sysfs reports the id of the 
isapnpdevice in a "string" form, like PNP0501. And I'm not able to convert it 
in the Vendor and Function hex form with a bash script.

if they don't exists then "procfs" is used. The vendor and function hex value 
are retrieved from "/proc/bus/pnp/devices" and sent to the isapnp.agent

isapnp.agent:
This agent act like the pci agent.

I hope it'll be useful.

Bye!
-- 
Simone Gotti
<simone.gotti@email.it>

[-- Attachment #2: hotplug.functions.patch --]
[-- Type: text/x-diff, Size: 1640 bytes --]

--- hotplug.functions	2004-04-10 18:53:02.000000000 +0200
+++ hotplug.functions.isapnp	2004-04-10 18:50:16.150626368 +0200
@@ -77,14 +77,20 @@
     FILENAME=$2
     DESCRIPTION=$3
 
+	case $TYPE in
+	isapnp)
+		LISTER=`which ${TYPE}modules 2> /dev/null` 
+		;;
+	*)
     # should we use usbmodules, pcimodules?  not on 2.5+, because sysfs
     # ought to expose the data we need to find all candidate drivers.
     # (on 2.5.48 it does for usb; but maybe not yet for pci.)
     case "$KERNEL" in
-    2.2*|2.3*|2.4*)	LISTER=`which ${TYPE}modules` ;;
+    2.2*|2.3*|2.4*)	LISTER=`which ${TYPE}modules 2> /dev/null` ;;
     *)			LISTER="" ;;
     esac
-
+	esac
+	
     if [ "$LISTER" != "" ]; then
 	# lister programs MIGHT be preferable to parsing from shell scripts:
 	# - usbmodules used for (a) multi-interface devices, (b) coldplug
@@ -105,12 +111,30 @@
 	    debug_mesg "pcimodules is scanning more than $PCI_SLOT ..."
 	    DRIVERS=`$LISTER`
 	    ;;
+	isapnp)
+		if [ "$ISAPNP_ID" != "" ]; then 
+		debug_mesg "isapnpmodules is scanning for the ISAPNP Id $ISAPNP_ID ..."
+	    DRIVERS=`$LISTER --id $ISAPNP_ID`
+		elif [ "$ISAPNP_STRING" != "" ]; then 
+		debug_mesg "isapnpmodules is scanning for the ISAPNP String $ISAPNP_STRING ..."
+	    DRIVERS=`$LISTER --string $ISAPNP_STRING`
+		fi
+	    ;;
 	esac
     fi
 
     # try parsing by shell scripts if no luck yet
     if [ "$DRIVERS" = "" ]; then
+	case $TYPE in
+	isapnp)
+		if [ "$LISTER" = "" ]; then
+		${TYPE}_map_modules < $FILENAME
+		fi
+		;;
+	*)
 	${TYPE}_map_modules < $FILENAME
+	;;
+	esac
     fi
 
     # FIXME remove dups and blacklisted modules from $DRIVERS here

[-- Attachment #3: isapnp.agent --]
[-- Type: application/x-shellscript, Size: 2196 bytes --]

[-- Attachment #4: isapnp.rc --]
[-- Type: application/x-shellscript, Size: 2006 bytes --]

[-- Attachment #5: isapnpmodules-0.1.tar.bz2 --]
[-- Type: application/x-tbz, Size: 3151 bytes --]

Re: Little script for ISAPNP hotplug

[Simone Gotti]

[-- Attachment #1: Type: text/plain, Size: 712 bytes --]

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.

I've also found the bottleneck that made the bash parser very slow.

So NOW the C parser isn't needed anymore, and the patch for hotplug.function 
was removed to.

Now all works only with the 2 script: isapnp.rc and isapnp.function.

I can't test it with a 2.4 kernel because I don't find the .config option for 
enabling the procfs isapnp support. 
I can't find the dir  /proc/usb/pnp or /proc/usb/isapnp so I can't test it, 
I'll try again leter. Can someone tell me what is this option?

Thanks.

Bye!
-- 
Simone Gotti
<simone.gotti@email.it>

[-- Attachment #2: isapnp.agent --]
[-- Type: application/x-shellscript, Size: 2187 bytes --]

[-- Attachment #3: isapnp.rc --]
[-- Type: application/x-shellscript, Size: 2846 bytes --]

Re: Little script for ISAPNP hotplug

[Alexander E. Patrakov]

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

Re: Little script for ISAPNP hotplug

[Simone Gotti]

[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]

On Monday 12 April 2004 04:25, Alexander E. Patrakov wrote:
> 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.

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. 

> 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.

Now I've removed it, Like I've said I can't test it with a 2.4 kernel because 
I can't find the /proc/bus/pnp/ or /proc/bus/isapnp/  dirs. While with 2.6 
the dir /proc/bus/pnp/ exists. 
Does the 2.4 kernels works in a different way with isapnp? My motherboard has 
12 isapnp devices but with 2.4 none is showed...

Bye and Thanks again!
-- 
Simone Gotti
<simone.gotti@email.it>

[-- Attachment #2: isapnp.agent --]
[-- Type: application/x-shellscript, Size: 2277 bytes --]

[-- Attachment #3: isapnp.rc --]
[-- Type: application/x-shellscript, Size: 2848 bytes --]

Re: Little script for ISAPNP hotplug

[Alexander E. Patrakov]

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`
                                                                                

Also, I don't see any attempt to follow "0xffff matches everything" rule.

-- 
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

Re: Little script for ISAPNP hotplug

[Simone Gotti]

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

Re: Little script for ISAPNP hotplug

[Simone Gotti]

Hi to All,

I've got various questions (and some people made me the same on the gentoo 
forums). 
I've noticed that a lot of people, like me, will be very happy if all of their 
modules will be autoloaded by hotplug.

I've noticed that for example the psmouse module doesn't export any 
MODULE_DEVICE_TABLE.

Looking at /proc/bus/pnp there's this line:

0a PNP0f13 PS/2 port for PS/2-style mice

So I think that if we add a MODULE_DEVICE_TABLE with this entry to psmouse.c 
this will be loaded by hotplug using my scripts. Is this the right way to do 
this thing? 

The same is for the PC Speaker (drivers/input/misc/pcspkr.c):
05 PNP0800 AT-style speaker sound

The Real Time Clock (rtc.c):
03 PNP0b00 AT real-time clock

I think that using my isapnp agent + rc, and a patch for these files will make 
at least the coldplugging work.
And If it works does a patch will be appreciated?

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

Re: Little script for ISAPNP hotplug

[Simone Gotti]

[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]

I did these patches.
They were tested by some people on the gentoo Italian forums with my hotplug 
agent and they worked well.

This is a copy of the mail that I sent to Vojtech Pavlik:

[start]
Hi,

Some days ago I've did an hotplug agent for isapnp devices. I've noticed that 
there wasn't an hotplug agent for this kind of devices and for this reason 
all the modules for isapnp devices weren't loaded by hotplug.

I've did this agent (that is attached) and now I can manage the coldplugging 
of modules like 8250_pnp, parport_pc, ns558 etc...

I've noticed that there are some modules using ISA devices (or at least I 
think) that aren't loaded by my hotplug scripts because they aren't "hotplug 
compliant". 
They don't export any isapnp id via the MODULE_DEVICE_TABLE macro and so the 
file /lib/modules/`uname -r`/modules.isapnpmap hasn't any information on 
which module to load. 
 
I've found 3 of this modules: 
 
psmouse (The PSmouse module) 
pcspkr (PC Speaker) 
rtc (real time clock) 
 
I know that you are the mantainer of the input subsystem so I'm writing to you 
for the first 2 modules.

For the psmouse modules, I don't know it this is the right way to do the 
things because I'm not very expert and I don't know if there are other busses 
(like PCI) for managing PS connectors.
 
The patches are against kernel 2.6.5.

Do you think that these are right and they can be usefull?

Thanks for your time.
[end]

I hope this can be useful.

Bye!
-- 
Simone Gotti
<simone.gotti@email.it>

[-- Attachment #2: isapnp.agent --]
[-- Type: application/x-shellscript, Size: 2277 bytes --]

[-- Attachment #3: isapnp.rc --]
[-- Type: application/x-shellscript, Size: 2848 bytes --]

[-- Attachment #4: psmouse-base-isapnpsupport.diff --]
[-- Type: text/x-diff, Size: 672 bytes --]

--- linux-2.6.5/drivers/input/mouse/psmouse-base.c	2004-04-04 18:08:37.000000000 +0200
+++ linux-2.6.5-prova01/drivers/input/mouse/psmouse-base.c	2004-04-19 10:37:56.000000000 +0200
@@ -18,6 +18,7 @@
 #include <linux/input.h>
 #include <linux/serio.h>
 #include <linux/init.h>
+#include <linux/pnp.h>
 #include "psmouse.h"
 #include "synaptics.h"
 #include "logips2pp.h"
@@ -739,5 +740,13 @@
 	serio_unregister_device(&psmouse_dev);
 }
 
+static const struct pnp_device_id pnp_dev_table[] = {
+	/* PS/2 port for PS/2-style mice */
+	{	"PNP0f13",		0	},
+	{	"",			0	}
+};
+
+MODULE_DEVICE_TABLE(pnp, pnp_dev_table);
+
 module_init(psmouse_init);
 module_exit(psmouse_exit);

[-- Attachment #5: pcspkr-isapnpsupport.diff --]
[-- Type: text/x-diff, Size: 658 bytes --]

--- linux-2.6.5/drivers/input/misc/pcspkr.c	2004-04-19 11:26:59.000000000 +0200
+++ linux-2.6.5-prova01/drivers/input/misc/pcspkr.c	2004-04-21 14:27:59.503811584 +0200
@@ -16,6 +16,7 @@
 #include <linux/module.h>
 #include <linux/init.h>
 #include <linux/input.h>
+#include <linux/pnp.h>
 #include <asm/io.h>
 
 MODULE_AUTHOR("Vojtech Pavlik <vojtech@ucw.cz>");
@@ -90,5 +91,13 @@
         input_unregister_device(&pcspkr_dev);
 }
 
+static const struct pnp_device_id pnp_dev_table[] = {
+	/* AT-style speaker sound */
+	{	"PNP0800",		0	},
+	{	"",			0	}
+};
+
+MODULE_DEVICE_TABLE(pnp, pnp_dev_table);
+
 module_init(pcspkr_init);
 module_exit(pcspkr_exit);

[-- Attachment #6: rtc-isapnpsupport.diff --]
[-- Type: text/x-diff, Size: 617 bytes --]

--- linux-2.6.5/drivers/char/rtc.c	2004-04-04 18:08:34.000000000 +0200
+++ linux-2.6.5-prova01/drivers/char/rtc.c	2004-04-19 10:59:35.000000000 +0200
@@ -77,6 +77,7 @@
 #include <linux/sysctl.h>
 #include <linux/wait.h>
 #include <linux/bcd.h>
+#include <linux/pnp.h>
 
 #include <asm/current.h>
 #include <asm/uaccess.h>
@@ -1346,6 +1347,14 @@
 }
 #endif
 
+static const struct pnp_device_id pnp_dev_table[] = {
+	/* AT real-time clock */
+	{	"PNP0b00",		0	},
+	{	"",			0	}
+};
+
+MODULE_DEVICE_TABLE(pnp, pnp_dev_table);
+
 MODULE_AUTHOR("Paul Gortmaker");
 MODULE_LICENSE("GPL");
 MODULE_ALIAS_MISCDEV(RTC_MINOR);

Re: Little script for ISAPNP hotplug

[Marco d'Itri]

On Apr 22, Simone Gotti <simone.gotti@email.it> wrote:

> I've did this agent (that is attached) and now I can manage the coldplugging 
> of modules like 8250_pnp, parport_pc, ns558 etc...
Your work is very interesting, it could help automatically loading some
of the drivers which currently cannot be autodetected and annoy udev
users (e.g. 8250, rtc, parport and floppy).

-- 
ciao, |
Marco | [5916 cau4zKUcMSxXw]


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg\x12297
_______________________________________________
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

Re: Little script for ISAPNP hotplug

[Simone Gotti]

On Thursday 22 April 2004 21:28, Marco d'Itri wrote:
> On Apr 22, Simone Gotti <simone.gotti@email.it> wrote:
> > I've did this agent (that is attached) and now I can manage the
> > coldplugging of modules like 8250_pnp, parport_pc, ns558 etc...
>
> Your work is very interesting, it could help automatically loading some
> of the drivers which currently cannot be autodetected and annoy udev
> users (e.g. 8250, rtc, parport and floppy).

Thanks a lot. This was the reason I've did it.
A lot of people on gentoo were experimenting with a full modular, full udev 
kernel and noticed these problems.
I know you are a debian developer so I'll be happy if you can get some 
feedback on it.

Like I've said I use it with 2.6 kernels, I don't know if it can be used with 
2.4 kernel too.

If you are interest I did a full description on how to make it work (kernel 
config, needed packages) here (It's a general description (not gentoo only)).

In English:
http://forums.gentoo.org/viewtopic.php?t\x161104

In Italian:
http://forums.gentoo.org/viewtopic.php?t\x160212


Bye!
-- 
Simone Gotti
<simone.gotti@email.it>




-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg\x12297
_______________________________________________
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

Re: Little script for ISAPNP hotplug

[Bill Nottingham]

Marco d'Itri (md@Linux.IT) said: 
> On Apr 22, Simone Gotti <simone.gotti@email.it> wrote:
> 
> > I've did this agent (that is attached) and now I can manage the coldplugging 
> > of modules like 8250_pnp, parport_pc, ns558 etc...
> Your work is very interesting, it could help automatically loading some
> of the drivers which currently cannot be autodetected and annoy udev
> users (e.g. 8250, rtc, parport and floppy).

Well, it can certainly detect the floppy *controller*. The drive
is still stuck as 'whatever the BIOS configured', yes?

Bill


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg\x12297
_______________________________________________
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

Re: Little script for ISAPNP hotplug

[Marco d'Itri]

On Apr 23, Bill Nottingham <notting@redhat.com> wrote:

> > Your work is very interesting, it could help automatically loading some
> > of the drivers which currently cannot be autodetected and annoy udev
> > users (e.g. 8250, rtc, parport and floppy).
> Well, it can certainly detect the floppy *controller*. The drive
> is still stuck as 'whatever the BIOS configured', yes?
Yes. On my own system the floppy controller is reported to be present,
even if there is no drive attached to it.
Anyway this is better than hardcoding a list of modules to load
unconditionally, which is the only other approach which has been
suggested...


FYI, this is the list of assigned IDs:

http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/devids.txt

(I wonder if keyboard reporting actually works, this could be
interesting for the GNOME/X people.)

-- 
ciao, |
Marco | [5929 prGBjlEoau9y2]


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg\x12297
_______________________________________________
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

Re: Little script for ISAPNP hotplug

[Bill Nottingham]

Marco d'Itri (md@Linux.IT) said: 
> > Well, it can certainly detect the floppy *controller*. The drive
> > is still stuck as 'whatever the BIOS configured', yes?
> Yes. On my own system the floppy controller is reported to be present,
> even if there is no drive attached to it.
> Anyway this is better than hardcoding a list of modules to load
> unconditionally, which is the only other approach which has been
> suggested...

Build it into the kernel. :)

> FYI, this is the list of assigned IDs:
> 
> http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/devids.txt
> 
> (I wonder if keyboard reporting actually works, this could be
> interesting for the GNOME/X people.)

It's certainly incomplete; only handles a few layouts. Moreover,
I don't see how it would work in the context of USB and other
connectors.

Bill


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg\x12297
_______________________________________________
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

Re: Little script for ISAPNP hotplug

[Simone Gotti]

On Friday 23 April 2004 18:19, Bill Nottingham wrote:
> Marco d'Itri (md@Linux.IT) said:
> > On Apr 22, Simone Gotti <simone.gotti@email.it> wrote:
> > > I've did this agent (that is attached) and now I can manage the
> > > coldplugging of modules like 8250_pnp, parport_pc, ns558 etc...
> >
> > Your work is very interesting, it could help automatically loading some
> > of the drivers which currently cannot be autodetected and annoy udev
> > users (e.g. 8250, rtc, parport and floppy).
>
> Well, it can certainly detect the floppy *controller*. The drive
> is still stuck as 'whatever the BIOS configured', yes?
>
> Bill

The floppy module doesn't export any isapnp ids, so by now it can't be 
autoloaded. 
My script (like all hotplug scripts) find that there's a floppy controller 
reading from /sys/bus/pnp/devices, but then in modules.isapnpmap there's 
nothing that tell what module is related to that IDs.

I don't know how the floppy module works, I don't know if these module is 
related only to isapnp floopy controller or it manage other kinds.

If it's only related to isapnp floppy controllers then it can easily patched 
like I've did with rtc, pcspkr and psmouse. 
If you are sure that this is the right way to do the things I'll do a patch 
for it too.

Bye!
-- 
Simone Gotti
<simone.gotti@email.it>


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg\x12297
_______________________________________________
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

Re: Little script for ISAPNP hotplug

[Simone Gotti]

On Friday 23 April 2004 18:19, Bill Nottingham wrote:
> Marco d'Itri (md@Linux.IT) said:
> > On Apr 22, Simone Gotti <simone.gotti@email.it> wrote:
> > > I've did this agent (that is attached) and now I can manage the
> > > coldplugging of modules like 8250_pnp, parport_pc, ns558 etc...
> >
> > Your work is very interesting, it could help automatically loading some
> > of the drivers which currently cannot be autodetected and annoy udev
> > users (e.g. 8250, rtc, parport and floppy).
>
> Well, it can certainly detect the floppy *controller*. The drive
> is still stuck as 'whatever the BIOS configured', yes?
>
> Bill

The floppy module doesn't export any isapnp ids, so by now it can't be 
autoloaded. 
My script (like all hotplug scripts) find that there's a floppy controller 
reading from /sys/bus/pnp/devices, but then in modules.isapnpmap there's 
nothing that tell what module is related to that IDs.

I don't know how the floppy module works, I don't know if these module is 
related only to isapnp floopy controller or it manage other kinds.

If it's only related to isapnp floppy controllers then it can easily patched 
like I've did with rtc, pcspkr and psmouse. 
If you are sure that this is the right way to do the things I'll do a patch 
for it too.

Bye!
-- 
Simone Gotti
<simone.gotti@email.it>


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg\x12297
_______________________________________________
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