lkml.org 
[lkml]   [2007]   [May]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: RTC_DRV_CMOS can break userspace interface
    On Sun, May 27, 2007 at 08:03:51PM +0100, Matthew Garrett wrote:

    > (It doesn't really help that rtc-cmos doesn't load on this machine, but
    > I'll try to track that down later - right now I suspect some sort of PNP
    > issue)

    Ah, no, it's because the ioports for the rtc-cmos driver are already
    claimed by the old driver from CONFIG_RTC. The following configuration
    is valid in Kconfig:

    CONFIG_RTC=y
    CONFIG_RTC_CMOS=m

    but will disable /proc/acpi/wakeup. It'll also be impossible to load
    CONFIG_RTC_CMOS because CONFIG_RTC has grabbed the io ports, so it's not
    possible to use the new interface. This situation doesn't appear to be
    documented, which is less than ideal...

    --
    Matthew Garrett | mjg59@srcf.ucam.org
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-05-28 01:41    [W:0.020 / U:0.072 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site