Sorry for my ignonrance in Comedi.
What i mean is why cannot you use the uevent in the kernel itself.
This does not mean to rewriting comedi. Might be comedi_config can
associate the driver which is based on the uevent.
Something like this,
Comedi_Config.c
__init int register_comedi_XXX(){
register_firmware_proc();
......
}
void handle_device(){
switch(device){
case 'devname': load_firmware_device_xxx();
break;
case 'end':
break;
}
}
__cleanup void unregister_comedi_XXX(){
unregister_firmware_proc();
.....
}
> > Why cannot be the /proc interface be used.
> Can you explain that a bit more.
Yes, What I mean to say is that one could /proc filesystem to interface
with the firmware. I presume that the firmware is something you are trying
out as enhancement to comedi. This would be an /proc/comedi/dev[0-9 a-z A-Z]+
situation where in the firmware gets fired. This does not need any
sort of change
to the Comedi Code itself.
Again i am taking an very big guess that comedi is being modified only to add
an firmware routine and not being done in the driver itself.
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
