9b32afa9f2
Previously we were loading kernel modules on all device events save for "remove". With the introduction of KOBJ_BIND/KOBJ_UNBIND this causes issues, as driver modules that have devices bound to their drivers get immediately reloaded, and it appears to the user that module unloading does not work. Let's change the rules to only load modules on "add" events instead.
14 lines
615 B
Plaintext
14 lines
615 B
Plaintext
# do not edit this file, it will be overwritten on update
|
|
|
|
ACTION!="add", GOTO="drivers_end"
|
|
|
|
ENV{MODALIAS}=="?*", RUN{builtin}+="kmod load $env{MODALIAS}"
|
|
SUBSYSTEM=="tifm", ENV{TIFM_CARD_TYPE}=="SD", RUN{builtin}+="kmod load tifm_sd"
|
|
SUBSYSTEM=="tifm", ENV{TIFM_CARD_TYPE}=="MS", RUN{builtin}+="kmod load tifm_ms"
|
|
SUBSYSTEM=="memstick", RUN{builtin}+="kmod load ms_block mspro_block"
|
|
SUBSYSTEM=="i2o", RUN{builtin}+="kmod load i2o_block"
|
|
SUBSYSTEM=="module", KERNEL=="parport_pc", RUN{builtin}+="kmod load ppdev"
|
|
KERNEL=="mtd*ro", ENV{MTD_FTL}=="smartmedia", RUN{builtin}+="kmod load sm_ftl"
|
|
|
|
LABEL="drivers_end"
|