From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HZ: 300Hz support
Date: 10 Nov 2006 09:35:17 +0100 [thread overview]
Message-ID: <p73zmazitru.fsf@bingen.suse.de> (raw)
In-Reply-To: <1163018557.23956.92.camel@localhost.localdomain>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> Fix two things. Firstly the unit is "Hz" not "HZ". Secondly it is useful
> to have 300Hz support when doing multimedia work. 250 is fine for us in
> Europe but the US frame rate is 30fps (29.99 blah for pedants). 300
> gives us a tick divisible by both 25 and 30, and for interlace work 50
> and 60. It's also giving similar performance to 250Hz.
>
> I'd argue we should remove 250 and add 300, but that might be excess
> disruption for now.
If we go down that path I would like to have 256.
Why? There are still lots of systems with broken Interrupt 0 routing
and usually on those the RTC works just fine. But unfortunately RTC
can be only programmed to power of two frequencies. 256 would fit.
-Andi
next prev parent reply other threads:[~2006-11-10 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 20:42 [PATCH] HZ: 300Hz support Alan Cox
2006-11-08 20:48 ` Arjan van de Ven
2006-11-08 21:12 ` Alan Cox
2006-11-08 21:01 ` Jiri Slaby
2006-11-08 22:39 ` Willy Tarreau
2006-11-10 8:35 ` Andi Kleen [this message]
2006-11-10 12:10 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p73zmazitru.fsf@bingen.suse.de \
--to=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.