Changeset 4055

Timestamp:

10/14/07 16:13:45 (1 year ago)

Author:

hverkuil

Message:

More doc updates.

Files:

• xdriver/trunk/README (modified) (3 diffs)

xdriver/trunk/README

@@ +1 @@
+Compatibility
+=============
+
+Please read this carefully: the merging of ivtv and the ivtv
+framebuffer driver into the kernel introduced several changes which
+impact how you setup the X driver and what MythTV version you can
+use.
+
+This X11 driver supports all ivtv versions >= 0.10. If you are using
+ivtv >= 1.0.0 and you want to use MythTV, then you need to get the
+MythTV subversion trunk or the mythtv-vid branch. The current MythTV
+release (0.20.2) only supports ivtv versions < 1.0.0.
+
+If you use ivtv < 1.0.0 and you are using MythTV <= 0.20.2 (i.e., you
+are not using the MythTV subversion trunk or the mythtv-vid branch), then
+you must set the osd_compat=1 option for the ivtv-fb module. This is the
+only time you need to do this. See the osd_compat section at the bottom
+if you need this, since it impacts the X configuration file.
+
+There is a bug in the ivtv-1.0.0 driver in kernel 2.6.22 that will make
+MythTV from the MythTV subversion trunk or the mythtv-vid branch hit a
+locking error occasionally. This is fixed in kernel 2.6.23 and the fix
+is also expected to go into kernel 2.6.22.11. Kernels < 2.6.22 are fine.
+
+Note that the name of the ivtv framebuffer kernel module changed:
+it is called ivtvfb for ivtv >= 1.0.0 and ivtv-fb for older ivtv versions.
+So if you use ivtv < 1.0.0 and you read 'ivtvfb' in the text below, then
+replace it with 'ivtv-fb'.
+
+The ivtv framebuffer driver can be obtained from www.ivtvdriver.org. It
+is part of the ivtv package. It will be merged with kernel 2.6.24.
+
-Xorg 7.x Servers
-================
@@ -148 +180 @@
-==================
-
+Note: Custom resolutions are only possible if the osd_compat module option was
+not specified with the ivtv-fb module. Setting that option locks down the
+resolution to a fixed value.
+
-If you want to use a custom resolution then you should first load the ivtvfb
-module with the resolutions you want. To do that add a line to
@@ -200 +236 @@
-'fbcon=vc:64-63', this will prevent any framebuffer device from being used
-for the console.
+
+However, in kernel 2.6.23 the 'vc:64-63' trick no longer works. Instead
+enable the VT_HW_CONSOLE_BINDING configuration option when compiling
+the kernel: 'Device Drivers', 'Character devices', 'Support for binding and
+unbinding console drivers'. You can now unload ivtvfb by running
+'rmmod -f ivtvfb' and the standard console will automatically be reattached.
+
+There may be more elegant methods of doing this, please let me know if
+you find one.
+
+
+ivtv-fb osd_compat option
+=========================
+
+If you are using ivtv < 1.0.0 and MythTV <= 0.20.2, then you have to set
+the osd_compat=1 option for the ivtv-fb module. This selects the framebuffer
+mode that MythTV expects (these MythTV versions hardcoded the framebuffer
+resolution and depth. If these would not match, then you would get a crash).
+
+In practice this means that the X configuration changes. Instead of having
+a section Mode "640x480" (PAL) or Mode "640x400" (NTSC) you now have to
+specify this:
+
+NTSC:
+
+Mode "720x480"
+    DotClock 23.832
+    HTimings 720 775 799 800
+    VTimings 480 494 496 497
+    Flags    "-HSync" "-VSync"
+EndMode
+
+PAL:
+
+Mode "720x576"
+    DotClock 23.721
+    HTimings 720 775 799 800
+    VTimings 576 590 592 593
+    Flags    "-HSync" "-VSync"
+EndMode
+
+And the Modes line in your Screen section also changes from "640x400" or
+"640x480" to "720x480" or "720x576" respectively.