On Saturday, July 20, 2013 02:34:58 PM Kay Sievers wrote:
> On Sat, Jul 20, 2013 at 1:47 PM, Kay Sievers wrote:
> > On Sat, Jul 20, 2013 at 12:56 PM, Rafael J. Wysocki wrote:
> >
> >> After a recent change present in 3.11-rc1 there is a driver, called
> >> processor,
> >> that can be bound to th
On Sat, Jul 20, 2013 at 1:47 PM, Kay Sievers wrote:
> On Sat, Jul 20, 2013 at 12:56 PM, Rafael J. Wysocki 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/de
Hi Kay,
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=p
On Saturday, July 20, 2013 12:56:54 PM Rafael J. Wysocki wrote:
> Hi Kay,
>
> 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,
On Sat, Jul 20, 2013 at 12:56 PM, Rafael J. Wysocki 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
