2011-12-01 12:17:22 +01:00
|
|
|
# do not edit this file, it will be overwritten on update
|
|
|
|
|
|
|
|
ACTION=="remove", GOTO="drivers_end"
|
|
|
|
|
rules: drivers - always call kmod, even when a driver is bound to the device
On Sat, Jul 20, 2013 at 12:56 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> After a recent change present in 3.11-rc1 there is a driver, called processor,
> that can be bound to the CPU devices whose sysfs directories are located under
> /sys/devices/system/cpu/. A side effect of this is that, after the driver has
> been bound to those devices, the kernel adds DRIVER=processor to ENV for CPU
> uevents and they don't match the default rule for autoloading modules matching
> MODALIAS:
>
> DRIVER!="?*", ENV{MODALIAS}=="?*", IMPORT{builtin}="kmod load $env{MODALIAS}"
>
> any more. However, there are some modules whose module aliases match specific
> CPU features through the modalias string and those modules should be loaded
> automatically if a compatible CPU is present. Yet, with the processor driver
> bound to the CPU devices the above rule is not sufficient for that, so we need
> a new default udev rule allowing those modules to be autoloaded even if the
> CPU devices have drivers.
2013-07-20 14:29:12 +02:00
|
|
|
ENV{MODALIAS}=="?*", RUN{builtin}="kmod load $env{MODALIAS}"
|
2013-03-16 09:26:47 +01:00
|
|
|
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"
|
2012-04-09 16:37:54 +02:00
|
|
|
SUBSYSTEM=="module", KERNEL=="parport_pc", RUN{builtin}="kmod load ppdev"
|
2013-03-16 09:26:47 +01:00
|
|
|
KERNEL=="mtd*ro", ENV{MTD_FTL}=="smartmedia", RUN{builtin}="kmod load sm_ftl"
|
2011-12-01 12:17:22 +01:00
|
|
|
|
|
|
|
LABEL="drivers_end"
|