linux-kernel - Re: [RFC][PATCH 03/10] arm: mxc: changes to common plat-mxc codeto add support for i.MX5

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: <20091207200326.GU22533@pengutronix.de>
Date:	Mon, 7 Dec 2009 21:03:26 +0100
From:	Robert Schwebel <r.schwebel@...gutronix.de>
To:	Herring Robert-RA7055 <ra7055@...escale.com>
Cc:	Sascha Hauer <s.hauer@...gutronix.de>,
	Amit Kucheria <amit.kucheria@...onical.com>,
	List Linux Kernel <linux-kernel@...r.kernel.org>,
	grant.likely@...retlab.ca, valentin.longchamp@...l.ch,
	daniel@...aq.de, Nguyen Dinh-R00091 <R00091@...escale.com>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC][PATCH 03/10] arm: mxc: changes to common plat-mxc codeto
	add support for i.MX5

Rob,

On Mon, Dec 07, 2009 at 10:17:52AM -0700, Herring Robert-RA7055 wrote:
> Sorry, my mistake. Sasha is correct that MX27 is v1 and MX25 is v2.
> 
> timer_is_v1 is just !timer_is_v2, so really only one is needed. I would
> define it like this to avoid having to change the timer code again for
> any new chips:
> 
> #define timer_is_v2()   (!(cpu_is_mx1() || cpu_is_mx21() ||
> cpu_is_mx27()))

Are you sure that FSL won't invent a v3 timer in the future?

rsc
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
--
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/