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]
Message-ID: <20090129211159.78714c5c@i1501.lan.towertech.it>
Date:	Thu, 29 Jan 2009 21:11:59 +0100
From:	Alessandro Zummo <alessandro.zummo@...ertech.it>
To:	rtc-linux@...glegroups.com
Cc:	eswierk@...stanetworks.com, tglx@...utronix.de, mingo@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [rtc-linux] Re: [PATCH] x86: i2c rtc instead of cmos rtc

On Thu, 29 Jan 2009 12:05:26 -0800
Ed Swierk <eswierk@...stanetworks.com> wrote:

> Would you prefer a single option to select the rtc (something like
> rtc.device={cmos|i2c,ds1339,1,0x68})? Or do you object to any option
> at all?

 I object to options of this kind. It took us a lot of efforts to move
 to the new i2c model and to the concept that devices have to be declared
 in the board support code. This kind of hack is in the opposite direction.

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ