| Message ID | CALdTtnvMFJfDK8dhbZjZugfO9x6EBAijk90aebYGMrQOL8fMeQ@mail.gmail.com |
|---|---|
| State | New |
| Headers | show |
Why is CONFIG_RTC_DRV_EFI a tristate variable if it doesn't work as a module ?
On Fri, May 20, 2016 at 7:44 AM, Tim Gardner <tim.gardner@canonical.com> wrote: > Why is CONFIG_RTC_DRV_EFI a tristate variable if it doesn't work as a > module ? Sorry - just noticed this question! It does work fine as a module. The problem is that the rtc-systohc driver, which sets the system clock in early boot, will only be able to make use of RTC drivers that are statically linked. -dann
Looks like this regressed since trusty - I've added an annotation this time to document it. Note that upstream disables this driver on x86 via Kconfig, thus the top level =y. BugLink: http://bugs.launchpad.net/bugs/158373 The following changes since commit 7be4369bae56cd3afe115a936f8d2edbbf6fd1ef: UBUNTU: [Config] Modularize some CRYPTO (2016-05-19 12:58:30 -0600) are available in the git repository at: git://git.launchpad.net/~dannf/ubuntu/+source/linux/+git/unstable 2643c95585fd1e3338023ba0083d789d2218d369 for you to fetch changes up to 2643c95585fd1e3338023ba0083d789d2218d369: UBUNTU: [Config] Link rtc-efi statically on arm64 (2016-05-19 14:17:56 -0600) ---------------------------------------------------------------- dann frazier (1): UBUNTU: [Config] Link rtc-efi statically on arm64 debian.master/config/annotations | 3 ++- debian.master/config/config.common.ubuntu | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-)