PAL TV-out & overscan support for xorg ati driver

[sebos69]

use xrandr. run xrandr --verbose to see the output options.

xrandr --output S-video --set tv_standard pal
xrandr --output S-video --set tv_vertical_position 3
etc.

Alex

thanks a lot, Alex.

finally, I remember I had to patch the driver to get rid of the missing stripe on the right part of the screen.

xrandr does not solve this issue (e.g. setting tv_horizontal_position to -5 still leaves a hidden portion (note : tvo_set did not solve that issue neither)

Are any other people experiencing this problem?

edit: here is the link where I give a working patched file:

http://ubuntuforums.org/showpost.php?p=3322594&postcount=89

[agd5f]

thanks a lot, Alex.

finally, I remember I had to patch the driver to get rid of the missing stripe on the right part of the screen.

xrandr does not solve this issue (e.g. setting tv_horizontal_position to -5 still leaves a hidden portion (note : tvo_set did not solve that issue neither)

Are any other people experiencing this problem?

edit: here is the link where I give a working patched file:
http://ubuntuforums.org/showpost.php...4&postcount=89

try adjusting tv_horizontal_size as well.

Alex

[sebos69]

try adjusting tv_horizontal_size as well.

Alex

I did, the image, does shrink, but the same missing part of the screen remains. It looks like this part of the screen is just not taken into account.


I don't know if it can help, but here is some information given by xrandr --verbose:

for the git driver:
Screen 0: minimum 320 x 200, current 800 x 600, maximum 800 x 800
VGA-0 disconnected (normal left inverted right)
Identifier: 0x4c
Timestamp: 1200971333
Subpixel: no subpixels
Clones:
CRTCs: 0 1
load_detection: 1 (0x00000001) range: (0,1)
DVI-0 disconnected (normal left inverted right)
Identifier: 0x4d
Timestamp: 1200971333
Subpixel: no subpixels
Clones:
CRTCs: 0 1
dvi_monitor_type: auto
scaler: off
tmds_pll: bios
load_detection: 1 (0x00000001) range: (0,1)
S-video connected 800x600+0+0 (0x4f) normal (normal left inverted right) 0mm x 0mm
Identifier: 0x4e
Timestamp: 1200971333
Subpixel: no subpixels
Clones:
CRTC: 0
CRTCs: 0 1
tv_standard: pal
tv_vertical_position: 0 (0x00000000) range: (-5,5)
tv_horizontal_position: 0 (0x00000000) range: (-5,5)
tv_horizontal_size: 0 (0x00000000) range: (-5,5)
load_detection: 1 (0x00000001) range: (0,1)
800x600 (0x4f) 38.2MHz -HSync +VSync
h: width 800 start 832 end 912 total 1024 skew 0 clock 37.4KHz
v: height 600 start 603 end 607 total 624 clock 59.9Hz
800x600 (0x50) 40.0MHz +HSync +VSync
h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz
v: height 600 start 601 end 605 total 628 clock 60.3Hz


while with the patched (working) 6.6.3 driver :
Screen 0: minimum 400 x 300, current 800 x 600, maximum 800 x 600
default connected 800x600+0+0 (0x54) normal (normal) 0mm x 0mm
Identifier: 0x53
Timestamp: 1200813386
Subpixel: no subpixels
Clones:
CRTC: 0
CRTCs: 0
800x600 (0x54) 28.8MHz
h: width 800 start 0 end 0 total 800 skew 0 clock 36.0KHz
v: height 600 start 0 end 0 total 600 clock 60.0Hz
640x480 (0x55) 18.4MHz
h: width 640 start 0 end 0 total 640 skew 0 clock 28.8KHz
v: height 480 start 0 end 0 total 480 clock 60.0Hz
400x300 (0x56) 7.2MHz
h: width 400 start 0 end 0 total 400 skew 0 clock 18.0KHz
v: height 300 start 0 end 0 total 300 clock 60.0Hz

but maybe this is irrelevant as xrandr is recent...

[agd5f]

I did, the image, does shrink, but the same missing part of the screen remains. It looks like this part of the screen is just not taken into account.

I'm not sure I follow, maybe a picture would help. tv-out only supports 800x600 at the moment, so if your other monitor is 1024x768 or something larger, tv-out will only show part of the larger screen in clone mode.

[sebos69]

I'm not sure I follow, maybe a picture would help. tv-out only supports 800x600 at the moment, so if your other monitor is 1024x768 or something larger, tv-out will only show part of the larger screen in clone mode.

This computer is connected to only the TV, so I think I use only 800x600.

For the picture, I took my best keyboard:

 git                6.6.3+patch
***************   ***************
*             *   *             *
*         righ*   *        right*
*left         *   *left         *
*             *   *             *
***************   ***************
not good               good

the asterisks delimit the visible portion. Tweaking xrandr settings would provide other results (like the "l" in "left" missing) , but nothing made the "t" of "right" appear.

[sebos69]

Ok, I saw a fix in the last git commits about NTSC which seems related to horizontal position also, and it hinted me to the portion of the code I used to patch in GATOS.

this patch (against current git) solves the problem for me :

diff --git a/src/radeon_tv.c b/src/radeon_tv.c
index 51f21d0..fada9f2 100644
--- a/src/radeon_tv.c
+++ b/src/radeon_tv.c
@@ -161,7 +161,7 @@ static const TVModeConstants availableTVModes[] =
TV_STD_PAL, /* standard */
1144, /* horTotal */
706, /* verTotal */
- 812, /* horStart */
+ 799, /* horStart */
824, /* horSyncStart */
669, /* verSyncStart */
696700, /* defRestart */

maybe 799 is not the perfect value.

This parameter should definitely be hot-configurable, no?

[Skinkie]

Ok, I saw a fix in the last git commits about NTSC which seems related to horizontal position also, and it hinted me to the portion of the code I used to patch in GATOS.

this patch (against current git) solves the problem for me :

diff --git a/src/radeon_tv.c b/src/radeon_tv.c
index 51f21d0..fada9f2 100644
--- a/src/radeon_tv.c
+++ b/src/radeon_tv.c
@@ -161,7 +161,7 @@ static const TVModeConstants availableTVModes[] =
TV_STD_PAL, /* standard */
1144, /* horTotal */
706, /* verTotal */
- 812, /* horStart */
+ 799, /* horStart */
824, /* horSyncStart */
669, /* verSyncStart */
696700, /* defRestart */

maybe 799 is not the perfect value.

This parameter should definitely be hot-configurable, no?

While reading is, is it possible to use the entire vertical region, or is this hardware limitated? (I would like to write to the VBI on top en Bottom of the screen.)

[agd5f]

While reading is, is it possible to use the entire vertical region, or is this hardware limitated? (I would like to write to the VBI on top en Bottom of the screen.)

I don't know the tv-out hardware that well. There are registers for encoding vbi data, however, I don't know exactly how they are used.

Alex

[Skinkie]

I don't know the tv-out hardware that well. There are registers for encoding vbi data, however, I don't know exactly how they are used.

Alex

Can I find those in the published specs? If so I would love to develop for it

[sebos69]

Can I find those in the published specs? If so I would love to develop for it

I guess I could also give a (small) help, to tweak those registers...