Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757701Ab3DXDvr (ORCPT ); Tue, 23 Apr 2013 23:51:47 -0400 Received: from mail-wi0-f169.google.com ([209.85.212.169]:36745 "EHLO mail-wi0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757637Ab3DXDvq (ORCPT ); Tue, 23 Apr 2013 23:51:46 -0400 MIME-Version: 1.0 In-Reply-To: References: <517746E4.908@linaro.org> <51774F44.2060704@linaro.org> From: Kay Sievers Date: Wed, 24 Apr 2013 05:51:24 +0200 Message-ID: Subject: Re: CONFIG_RTC_HCTOSYS lost on x86 with ALWAYS_USE_PERSISTENT_CLOCK changes? To: John Stultz Cc: LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 830 Lines: 21 On Wed, Apr 24, 2013 at 5:33 AM, Kay Sievers wrote: > Also: > $ cat /sys/class/rtc/rtc0/hctosys > 0 > always carried "1", and this now breaks setups which expect an > automatically created symlink /dev/rtc to the actual "system rtc". We used to do this in upstream standard udev rules: SUBSYSTEM=="rtc", ATTR{hctosys}=="1", MODE="0644" http://cgit.freedesktop.org/systemd/systemd/tree/rules/50-udev-default.rules#n18 If that information is expected to be gone now, we need to update some tools. Whats' the proper way now to find the "system rtc" to use? Kay -- 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/