Changeset 4052

Timestamp:

10/12/07 10:39:23 (1 year ago)

Author:

hverkuil

Message:

Update README with info on how to configure X.

Files:

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

xdriver/trunk/README

@@ -11 +11 @@
-then it is likely that you are missing the xorg-server development
-package. For Fedora this package is called 'xorg-x11-server-sdk'.
+
-
-Xorg 6.x & Xfree86 servers
@@ -25 +26 @@
-X11 video drivers.
-
+
+X configuration
+===============
+
+The next step is to setup the X configuration to enable the X display.
+For Xorg the configuration file is /etc/X11/xorg.conf, for Xfree86
+the configuration file is /etc/X11/XF86Config.
+
+The default resolution of the framebuffer is 640x400 for NTSC and
+640x480 for PAL and SECAM. So the configuration differs between
+the two.
+
+For NTSC you should add the following to your X config file:
+
+------------------------- cut here -------------------------
+Section "Monitor"
+    Identifier     "NTSC Monitor"
+    HorizSync       10-68
+    VertRefresh     25-120
+
+    Mode "640x400"
+        DotClock    23.832
+        HTimings    640 735 759 800
+        VTimings    400 454 456 497
+        Flags      "-HSync" "-VSync"
+    EndMode
+EndSection
+
+Section "Device"
+    Identifier     "Hauppauge PVR-350 Framebuffer"
+    Driver         "ivtv"
+    Option         "fbdev" "/dev/fb0"      # <-- modify if using another device
+    BusID          "0:10:0"                # <-- obtain from lspci (see later)
+EndSection
+
+Section "Screen"
+    Identifier     "TV Screen"
+    Device         "Hauppauge PVR-350 Framebuffer"
+    Monitor        "NTSC Monitor"
+    DefaultDepth    24
+    DefaultFbBpp    32
+    SubSection     "Display"
+        Depth       24
+        FbBpp       32
+        Modes      "640x400"
+    EndSubSection
+EndSection
+------------------------- cut here -------------------------
+
+For PAL/SECAM you should add the following to your X config file:
+
+------------------------- cut here -------------------------
+Section "Monitor"
+    Identifier     "PAL Monitor"
+    HorizSync       10-68
+    VertRefresh     25-120
+
+    Mode "640x480"
+        DotClock    23.721
+        HTimings    640 735 759 800
+        VTimings    480 542 544 593
+        Flags      "-HSync" "-VSync"
+    EndMode
+EndSection
+
+Section "Device"
+    Identifier     "Hauppauge PVR-350 Framebuffer"
+    Driver         "ivtv"
+    Option         "fbdev" "/dev/fb0"      # <-- modify if using another device
+    BusID          "0:10:0"                # <-- obtain from lspci (see later)
+EndSection
+
+Section "Screen"
+    Identifier     "TV Screen"
+    Device         "Hauppauge PVR-350 Framebuffer"
+    Monitor        "PAL Monitor"
+    DefaultDepth    24
+    DefaultFbBpp    32
+    SubSection     "Display"
+        Depth       24
+        FbBpp       32
+        Modes      "640x480"
+    EndSubSection
+EndSection
+------------------------- cut here -------------------------
+
+In the "Device" section you will have to modify the Option field to select
+the correct framebuffer device (usually /dev/fb0 or /dev/fb1). You also have
+to obtain the correct BusID of the framebuffer device. To do that run:
+
+lspci | grep iTVC15
+
+You should get a line like this:
+
+06:02.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01)
+
+The numbers at the beginning form the BusID: 06:02.0 becomes "6:2:0" in the
+X config file. Note that lspci reports the numbers as hexadecimal where the
+BusID option expects them as decimal. So if lspci reports "01:0e.0", then
+BusID should be "1:14:0".
+
+The final step is to add the TV Screen to you server layout:
+
+Section "ServerLayout"
+    ...
+    Screen 0 "Screen 1"                      # << (your computer monitor)
+
+    # (add the following line)
+    Screen 1 "TV Screen" RightOf "Screen 1"  # << (TV screen)
+    ...
+EndSection
+
+If you want to use the TV Screen as the main display, then you can just use:
+
+    Screen 0 "TV Screen"
+  
+After restarting X you should see the X screen on your TV.
+
+
+Custom resolutions
+==================
+
+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
+/etc/modprobe.conf, e.g.:
+
+options ivtvfb osd_xres=720 osd_yres=576
+
+(Run 'modinfo ivtvfb' to see all module options.)
+
+Now load ivtvfb ('modprobe ivtvfb') and the new height and width will be used.
+
+Note that you should make sure that either X isn't started at all, or that
+X isn't using the PVR-350 framebuffer. You can get problems if the
+X configuration and the framebuffer have a mismatch regarding the resolution
+or timings.
+
+Next run 'fbset -x /dev/fbX' (replace /dev/fbX with the correct framebuffer
+device). That gives you a new Mode description, e.g.:
+
+Mode "720x576"
+    # D: 23.720 MHz, H: 29.650 kHz, V: 50.001 Hz
+    DotClock 23.721
+    HTimings 720 775 799 800
+    VTimings 576 590 592 593
+    Flags    "-HSync" "-VSync"
+EndMode
+
+Replace the "Mode" subsection in the "Monitor" section and update the
+Modes resolution in the "Screen" section.
+
+Start X and the new resolution should be used.
+
+You can also have multiple "Mode" subsections in "Monitor" and use xrandr to
+switch dynamically.
+
+
+How to prevent the console from using the framebuffer
+=====================================================
+
+By default when you load ivtvfb the framebuffer is used for the console
+output. Unfortunately, this is usually very annoying since this makes it
+hard to unload ivtvfb.
+
+You can prevent this by adding a magic incantation to the kernel options
+in your grub or lilo configuration.
+
+If your monitor console is using the framebuffer of you graphics cards,
+then you should use kernel option 'fbcon=vc:0-0'. This ensures that only
+the first framebuffer device (that of your graphics card) is used.
+
+If you don't use a framebuffer at all for your console, then use the option
+'fbcon=vc:64-63', this will prevent any framebuffer device from being used
+for the console.