linux-kernel - Re: [PATCH 04/27] asm-generic: add legacy I/O header files

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: <200905011529.04774.arnd@arndb.de>
Date:	Fri, 1 May 2009 15:29:04 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Russell King <rmk+lkml@....linux.org.uk>,
	Michal Simek <monstr@...str.eu>, linux-arch@...r.kernel.org,
	Remis Lima Baima <remis.developer@...glemail.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 04/27] asm-generic: add legacy I/O header files

On Friday 01 May 2009, Alan Cox wrote:
> Joining in late but its not at all highly PC specific. The same frequency
> is used for a whole pile of setups (Alpha etc). It's not well named but
> there are good sound reasons the PC chose 1193182 and while those reasons
> have long lapsed its a good frequency for other reasons nowdays.
> 
> The clock isn't for the PIC either - its for the PIT (although its used
> to clock various other things).
> 
> We actually have a define of PIT_TICK_RATE internal to the x86 port for
> those x86 cases that can use it.

How about this comment then:

/*
 * CLOCK_TICK_RATE is traditionally the base frequency using the PC-style
 * i8253 "PIT" timer. Architecture independent device drivers should not
 * rely on this value.
 * Any architecture that either has a real PC-style PIT, or does not have a
 * fixed timer interval at all and just needs to provide some value here
 * should just fall back to this default.
 */

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