[Openchrome-users] Overscan and mode selection on CN700 (Bartosz)

Fri Nov 20 15:34:05 PST 2009

Hello Daniel.
Please subscribe new bug at openchrome.org.
Try to add new modes at VT1625Modes function at via_vt162x.h file.
To calculate this tables, the cvt could be useful.
For example:
cvt 640 480

Best Regards
Bartosz Kosiorek

2009/11/14 Daniel Lawson <danjlawson2000 at yahoo.com>

> Hi all,
>
> I have a via CN10000EG board with a CN700 graphics chip and am trying to
> use it with openchrome for PAL tv-out.  Primarily I want to be able to
> overscan to remove a big black border, but more generally I've noticed that
> some of the supposed supported modes are not available so I think this may
> be a more general problem with my setup.
>
> The openchrome driver is the 0.2.904 from the downloads page, and xvmc etc
> are working, so the driver is at least mostly installed correctly.
>
> My understanding, from much googling, is that the correct modelines are
> available in the driver and have to be selected by setting:
> Modes     "640x480Over"
> in the screen/Display section of xorg.conf, where I currently have:
> Modes     "640x480"
> However, if I use this setting I get "No screens found".  This is true for
> "720x576Over" and "720x576NoScale" as well.  Looking in /var/log/Xorg.log I
> see:
>
> ~$ grep "Over" /var/log/Xorg.0.log
> (II) CHROME(0): Not using mode "800x600Over" (no mode of this name)
> (II) CHROME(0): Not using mode "720x576Over" (no mode of this name)
> (II) CHROME(0): Not using mode "640x480Over" (no mode of this name)
> ~$ grep -i "NoScale" /var/log/Xorg.0.log
> (II) CHROME(0): Not using mode "720x576NoScale" (no mode of this name)
> ~$ grep -i "ModeLine" /var/log/Xorg.0.log (and the lines before added, they
> might be relevant)
> (**) CHROME(0): *Built-in mode "640x480": 0.0 MHz, 37861.1 kHz, 73.3 Hz
> (II) CHROME(0): Modeline "640x480"x73.3    0.00  640 0 0 0  480 0 0 0
> (37861.1 kHz)
> (**) CHROME(0): *Built-in mode "720x576": 0.0 MHz, 35855.8 kHz, 60.6 Hz
> (II) CHROME(0): Modeline "720x576"x60.6    0.00  720 0 0 0  576 0 0 0
> (35855.8 kHz)
> (**) CHROME(0): *Built-in mode "800x600": 0.0 MHz, 48077.4 kHz, 72.7 Hz
> (II) CHROME(0): Modeline "800x600"x72.7    0.00  800 0 0 0  600 0 0 0
> (48077.4 kHz)
> (**) CHROME(0):  Built-in mode "720x540"
> (**) CHROME(0):  Built-in mode "720x480": 0.0 MHz, 29799.6 kHz, 60.5 Hz
> (II) CHROME(0): Modeline "720x480"x60.5    0.00  720 0 0 0  480 0 0 0
> (29799.6 kHz)
>
> The relevant sections of xorg.conf are at the end.  I'm confused as to why
> the X can't find the "640x480Over" etc.  I can see they are defined in
> via_vt162x.h, everywhere but the VT1625 tables (which I have).  So I tried
> replacing the "640x480" modeline with the VT1623 tables modeline in the two
> tables, which alas changes nothing.  I also tried changing the via_mode.h in
> the same way.
>
> All those 0's in the "built-in" section above are suspicious.  I wonder if
> none of the modes defined in the via_vt162x.h are being found, and X is
> using some internal fall back?
>
> Does anyone have any idea how to go about fixing this, or at least finding
> more out about where it is going wrong?
>
> Thanks
>
> Dan
>
> Xorg.conf snippet (Some of it is obviously unnecessary - I was trying
> things for the unichrome driver):
>
> Section "Monitor"
>         Identifier  "TV"
>         HorizSync    24.0 - 80.0
>         VertRefresh  50.0 - 74.0
> # Set for 16:9 display
>         DisplaySize     400 225
>
>         #Refresh Rate 60Hz
>         ModeLine "720x480" 26.7 720 736 808 896 480 481 484 497
>         ModeLine "720x576" 32.7 720 744 816 912 576 577 580 597
>         ModeLine "848x480" 31.5 848 864 952 1056 480 481 484 497
>         ModeLine "856x480" 31.7 856 872 960 1064 480 481 484 497
> EndSection
>
>
> Section "Device"
>         Identifier      "VIA"
>         Driver          "openchrome"
>     Option         "SWCursor" "on"
>     Option "TVOutput" "S-Video"
>         Option      "ActiveDevice" "TV"
>         Option          "VBEModes" "true"   # Comment in for TV-out
> EndSection
>
> Section "Screen"
>         Identifier "Default Screen"
>         Device     "VIA"
>         Monitor    "TV"
>         DefaultDepth     16
>         SubSection "Display"
>                 Viewport   0 0
>                 Depth     24
>                 Modes    "640x480" "720x576" "800x600" "800x600Over"
> "720x576Over" "720x576NoScale" "640x480Over"
>         EndSubSection
>         SubSection "Display"
>                 Depth     16
>                 Modes    "640x480" "720x576" "800x600" "800x600Over"
> "720x576Over" "720x576NoScale" "640x480Over"
>         EndSubSection
> EndSection
>

I have created a new tracker at: 

http://openchrome.org/trac/ticket/336

However, I tried to add modelines and couldn't get them to work.  This does not appear to be due to my modelines; I can't get the built in ones to work either.  I see a "720x480Over" in the via_vt162x.h file, and I added it to Xorg.conf, but it wasn't detected by X as a valid modeline name.  So I think the problem may lay in the translation of modelines to names somewhere (which of course might be specific to my configuration of X, though its unlikely).

Since I can't test my modelines I can't add them.  Also I wouldn't know if the modelines in the vt162x tables wouldn't be default, in which case they aught to be defined for vt1625 (just not detected?) so its possible my bug might not be getting at the correct root cause.

I'd appreciate any help tracking this down!

Thanks

Dan