linux-kernel - Re: [PATCH] x86: i2c rtc instead of cmos rtc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 29 Jan 2009 11:21:58 -0800
From:	Ed Swierk <eswierk@...stanetworks.com>
To:	Alessandro Zummo <alessandro.zummo@...ertech.it>
Cc:	rtc-linux@...glegroups.com, tglx@...utronix.de, mingo@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: i2c rtc instead of cmos rtc

On Tue, Jan 27, 2009 at 3:21 AM, Alessandro Zummo
<alessandro.zummo@...ertech.it> wrote:
>  can't you just avoid compiling rtc cmos? or compile it as a module and
>  load the i2c rtc first?

In our embedded application it's more convenient to build all the
drivers needed to support various hardware configurations into the
kernel, and avoid messing with modules. This works fine for devices
that can be detected dynamically, but RTC chips are among the few that
need to be configured statically; my change just relaxes the current
assumption that all x86 boards have a usable CMOS RTC.

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