diff options
author | Kay Sievers <kay@vrfy.org> | 2013-07-20 14:29:12 +0200 |
---|---|---|
committer | Kay Sievers <kay@vrfy.org> | 2013-07-20 14:31:53 +0200 |
commit | bf7f800f2b3e93ccd1229d4717166f3a4d3af72f (patch) | |
tree | 94a0967666da9d4fcbda5cb8558d2a7e4f346c32 /src/core/dbus.c | |
parent | e7c431d3bcfdeeec5dcae0707145edb9a3f749aa (diff) |
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.
Diffstat (limited to 'src/core/dbus.c')
0 files changed, 0 insertions, 0 deletions