# HG changeset patch # User diego # Date 1025475047 0 # Node ID 5e9b842fd06e4e4ee4c407bcd4ce1a01ac434091 # Parent 0b5a789d7fabca2d8879f64fe94af96dd0ddae61 further updates for RTC diff -r 0b5a789d7fab -r 5e9b842fd06e DOCS/documentation.html --- a/DOCS/documentation.html Sun Jun 30 20:34:54 2002 +0000 +++ b/DOCS/documentation.html Sun Jun 30 22:10:47 2002 +0000 @@ -664,25 +664,37 @@ usleep() to tune A/V sync, with +/- 10ms accuracy. However sometimes the sync has to be tuned even finer.
  • The new timer code uses PC's RTC (Real Time Clock) for this task, - because it has precise 1ms timers. This requires root privileges, or a - setuid root MPlayer binary. If you are running kernel - 2.4.19pre8 or later you can adjust the maximum RTC frequency for normal - users through the /proc filesystem. Use this command to enable - RTC for normal users: + because it has precise 1ms timers. It is automagically enabled when + available, but requires root privileges, a setuid root + MPlayer binary or a properly set up kernel. +
    + If you are running kernel 2.4.19pre8 or later you can adjust the maximum + RTC frequency for normal users through the /proc filesystem. + Use this command to enable RTC for normal users:

    - echo 1025 > /proc/sys/dev/rtc/max-user-freq + echo 1024 > /proc/sys/dev/rtc/max-user-freq

    If you do not have such a new kernel, you can also change one line in - drivers/char/rtc.c and recompile your kernel. Find the line -

    - if ((rtc_freq > 64) && (!capable(CAP_SYS_RESOURCE))) -

    + drivers/char/rtc.c and recompile your kernel. Find the + section that reads + 
    +	 * We don't really want Joe User enabling more
+	 * than 64Hz of interrupts on a multi-user machine.
+	 */
+	if ((rtc_freq > 64) && (!capable(CAP_SYS_RESOURCE)))
+
    and change the 64 to 1024. You should really know what you are doing, though.
    - You can see the new timer's efficiency in the status line. In some hardware - combinations (confirmed during usage of non-DMA DVD drive on an ALi1541 board) - usage of the RTC timer causes skippy playback. It's recommended to use the - following method in these cases.
    • + You can see the new timer's efficiency in the status line. +
    + The power management functions of some notebook BIOSes with speedstep CPUs + interact badly with RTC. Audio and video may get out of sync. Plugging the + external power connector in before you power up your notebook seems to help. + You can always turn off RTC support with the -nortc switch. + In some hardware combinations (confirmed during usage of non-DMA DVD + drive on an ALi1541 board) usage of the RTC timer causes skippy playback. + + It's recommended to use the following method in these cases.
  • The third timer code is turned on with the -softsleep option. It has the efficiency of the RTC, but it doesn't use RTC. On the other hand, it requires more CPU.
    • @@ -690,7 +702,7 @@ -Note: NEVER install setuid MPlayer binary on a +Note: NEVER install a setuid root MPlayer binary on a multiuser system! It's a clear way for everyone to gain root. diff -r 0b5a789d7fab -r 5e9b842fd06e DOCS/faq.html --- a/DOCS/faq.html Sun Jun 30 20:34:54 2002 +0000 +++ b/DOCS/faq.html Sun Jun 30 22:10:47 2002 +0000 @@ -432,7 +432,8 @@ Q:When I start playing, I get this message but everything seems fine:
    Linux RTC init: ioctl (rtc_pie_on): Permission denied -    A:You need root privileges to use the new timing code. For details see the +    A:You need root privileges or a +specially set up kernel to use the new timing code. For details see the installation section of the documentation.