* Re: [patch] input: Fix CLOCK_TICK_RATE usage ... [8/13]
@ 2003-06-18 18:50 David Mosberger
0 siblings, 0 replies; only message in thread
From: David Mosberger @ 2003-06-18 18:50 UTC (permalink / raw)
To: linux-ia64
>>>>> On Wed, 18 Jun 2003 09:47:44 -0500, Hollis Blanchard <hollisb@us.ibm.com> said:
Hollis> On Tuesday, Jun 17, 2003, at 18:24 US/Central, David Mosberger wrote:
>> #ifdef CONFIG_LEGACY_HW
>> # define PIT_FREQ 1193182
>> # define LATCH ((CLOCK_TICK_RATE + HZ/2) / HZ)
>> #endif
>> This way, machines that support legacy hardware can define
>> CONFIG_LEGACY_HW and on others, the macro can be left undefined, so
>> that any attempt to compile drivers requiring legacy hw would fail to
>> compile upfront (much better than accessing random ports!).
Hollis> Is "having legacy hardware" an all-or-nothing condition for you? If
Hollis> not, a CONFIG_LEGACY_PIT might be more appropriate...
I believe it is, though I'm not entirely certain about Intel's Tiger
platform. If more fine-grained distinction really is needed, I
suspect we'd rather want something called CONFIG_8259_PIT. Might be a
good idea to do this for all legacy devices.
--david
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-06-18 18:50 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-06-18 18:50 [patch] input: Fix CLOCK_TICK_RATE usage ... [8/13] David Mosberger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox