The claim that "That cpufreq driver fails gracefully on other (non IBM, OPAL) powerpc platforms that don't have the expected files in the device-tree" seems to imply it should be perfectly harmless on pre- power8 platforms. Of course, I'll put it through its paces on a couple such machines to make sure anyway. :P
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1324571 Title: powerpc: enable powernv-cpufreq as built-in (vs. module) Status in “linux” package in Ubuntu: Fix Committed Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Committed Bug description: The cpufreq driver for powernv is currently built as a module (powernv-cpufreq.ko; see bug 1309576). It is not automatically loaded in the boot process (even when included in the initrd). It is desirable to have it built-in so it automatically loads on systems booting in PowerNV mode. One of the reaons is to save power by default (the default cpufreq governor is ondemand). That cpufreq driver fails gracefully on other (non IBM, OPAL) powerpc platforms that don't have the expected files in the device-tree (see [2]). A patch will be sent to the kernel-team mailing list. Thanks. [1] https://lists.ubuntu.com/archives/kernel- team/2014-April/042431.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
