>> 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.
Before we have tons of choosable HZ possibilities, I prefer
http://lkml.org/lkml/2006/6/18/111 where the user can input his desired
value.
>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.
-`J'
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
